Age | Commit message (Collapse) | Author |
|
OK nicm@
|
|
OK nicm@
|
|
|
|
|
|
variable and memcpy() that value into 4 bytes of malloc()'d space
seems roundabout.
Just memcpy() a four byte constant string into the malloc()'d space
as required and kill putULong(). No functional change.
|
|
are plain local routes.
|
|
|
|
ok doug
|
|
(But leave the VMS workaround intact)
|
|
avoid fd_set overflows.
Back when I was young, I fixed these throughout the tree, and the world
continued on ignoring the issue... The malloc/free dance was used because
poll() was not very portable yet. Now poll() is commonplace, and we should
use this safer API.
ok guenther millert
|
|
(Both NetBSD and FreeBSD provide these prototypes)
ok millert@
|
|
dance which was used to avoid fd_set overflow with high file descriptor
values.
ok doug
|
|
|
|
Correct ASCII rendering: \(lb \(<> \(sd
Make ASCII rendering agree with groff, using backspace overstrike:
\(da \(ua \(dA \(uA \(fa \(c* \(c+ \(ib \(ip \(/_ \(pp \(is \(dd \(dg
|
|
with libevent.
this has been in snaps for a while without any negative (or positive)
feedback.
review and tweaks by bluhm@ nicm@
ok bluhm@ deraadt@
|
|
escape sequences just like it was earlier implemented for -Thtml.
Do not let control characters other than ASCII 9 (horizontal tab)
propagate to the output, even though groff allows them; but that
really doesn't look like a great idea.
Let mchars_num2char() return int such that we can distinguish invalid \N
syntax from \N'0'. This also reduces the danger of signed char issues
popping up.
|
|
mikeb@ in pfctl/parse.y rev 1.641.
with feedback from mikeb sthen and henning
|
|
representation, not for character escapes with unknown names.
According to groff, the latter produce no output, and we now warn
about them.
|
|
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
|
|
Accept only 0xXXXX, 0xYXXXX, 0x10XXXX with Y != 0.
This simplifies mchars_num2uc().
|
|
INADDR_BROADCAST the same as INADDR_ANY.
ok mpi
|
|
handle them. Also use M_NOWAIT for copying a multicast packet.
|
|
sesssion for multicast in proper way.
|
|
Without this, the packets larger than the minimum MTU on the routes to
the L2TP peer had been dropped.
|
|
ok jsing@ miod@
|
|
ok tedu@
|
|
|
|
ok doug@ jsing@
|
|
and -Thtml rendering of character escape sequences
|
|
with groff, in particular in cases where groff uses backspace overstrike.
In two cases, agreement is impossible because groff clobbers the
previous line: \(*G \(*S
In a number of cases, groff rendering is so misleading that i chose
to render differently: \(Sd \(TP \(Tp \(Po \(ps \(sc \(r! \(r? \(de
While here, also correct the \(la and \(ra Unicode code points.
|
|
be put on the ring couldnt be allocated.
this pulls the code that puts the mbufs on the ring out of myx_rx_fill
so it can return early if firstmb cant be allocated, which puts it
in the right place to return unused slots to the if_rxring.
this means myx rx wont lock up if you're DoSsed to the point where
you exhaust your mbuf pools and cant allocate mbufs for the ring.
ok jmatthew@
|
|
REGRESS_* idiom died a while ago
OK naddy@ sthen@
|
|
|
|
|
|
to cover the first 8 MB of memory such that it covers kernel .text and not
much else. This is a first step towards W^X in the kernel for machines
with G4 and older processors.
ok mpi@
|
|
specifications under certain circumstances resulting in potentially
elevated access permissions for IPv6 traffic. Reported by sthen@;
ok henning benno sthen
|
|
may end up in ${svc} by mistake.
OK ajacoutot@
|
|
Of course, this is only a minor improvement; it would be much better
to support non-ASCII characters in these output modes, but that
would require major changes that i'm not going to work on right now.
The main reason for doing this is that it allows to get ASCII output
closer to groff.
|
|
|
|
step towards W^X in the kernel, even though it is only effective on machines
with a G5 processor.
ok mpi@
|
|
|
|
ntoh[ls]()) obscure rather than simplify things. Especially when
they are used only once. Just use the expansion.
|
|
in one common, safe way instead of three different ways. In particular,
* skip NUL, it is used to mean "no output desired"
* deny 0x01-0x1F and 0x7F-0x9F, print REPLACEMENT CHARACTER instead
* print 0x20-0x7E literally or name-encoded, as required
* print characters above 0x9F numerically
|
|
this is relevant because we use the HTML output module
for man.cgi(8), where broken output can cause security issues.
|
|
an IPv4 address. Just memcpy() it.
|
|
known to break mice upon resume.
ok shadchin@
|
|
|
|
In UTF-8 output, do not print anything if mchars_spec2cp() returns 0.
In particular, this repairs handling of zero-width spaces (\&).
While here, let mchars_spec2cp() return 0xFFFD instead of -1
if the character is not found, simplifying the using code.
In HTML output, do not print obfuscated ASCII characters and
do not test for one-char escapes, mchars_spec2cp() already does that.
|
|
|
|
fault when it tries to get a new one.
Problem spotted by weerd@
|