| Age | Commit message (Collapse) | Author |
|---|
|
recently.
OK kspillner@
|
|
|
|
|
|
can be used or should be released by rtfree(9).
It currently checks if the route is UP and is not attached to a stall
ifa.
ok bluhm@, claudio@
|
|
hazard pointers were becoming corrupt and therefore panics.
the problem turned out to be that bridge_input calls if_input on
behalf of a hardware interface which then calls bpf_mtap at splsoftnet,
while the actual hardware nic calls if_input and bpf_mtap at splnet.
the hardware interrupts ran in the middle of the bpf calls bridge
runs at softnet. this means the same srps are being entered and
left on the same cpu at different ipls, which led to races because
of the order of operations on the per cpu hazard pointers.
after a lot of experimentation, jmatthew@ figured out how to deal
with this problem without introducing per cpu critical sections
(ie, splhigh) calls in srp_enter and srp_leave, and without introducing
atomic operations.
the solution is to iterate forward through the array of hazard
pointers in srp_enter, and backward in srp_leave to clear. if you
guarantee that you leave srps in the reverse order to entering them,
then you can use the same set of SRPs at different IPLs on the same
CPU.
the ordering requirement is a problem if we want to build linked
data structures out of srps because you need to hold a ref to the
current element containing the next srp to use it, before giving
up the current ref. we're adding srp_follow() to support taking the
next ref and giving up the current one while preserving the structure
of the hazard pointer list. srp_follow() does this by reusing the
hazard pointer for the current reference for the next ref.
both mattieu baptiste and jmatthew@ have been hitting this pretty
hard with a tweaked version of srp+bpf that uses srp_follow instead
of interleaved srp_enter/srp_leave sequences. neither can reproduce
the panics anymore.
thanks to mattieu for the report and tests
ok jmatthew@
|
|
Historically, \- was used in troff for three cases: flags/pathnames,
en dashes, and minus signs. mandoc_char(7) currently recommends it
for minus signs, recommends \(en for en dashes, and doesn't mention
flags/pathnames.
In the old days, nroff rendered \- as ASCII '-', and troff rendered
it as en dash/minus (which were visually indistinguishable).
In Unicode, en dashes and minus signs are semantically distinct and
encoded differently (U+2013 for en dash, U+2212 for minus), and
often rendered differently too. Meanwhile ASCII '-' has been renamed
"hyphen-minus" and fonts typically render it closest to a hyphen, not
a minus.
There is very little consistency across roff implementations and output
formats for what Unicode character \- corresponds to. So at least for
minus signs, change the recommendation to the unambiguous \(mi escape.
ok jmc@ (after reams of discussion)
|
|
|
|
|
|
|
|
ok deraadt
|
|
Actually using these is very stupid because they are groff extensions
and other roff(7) implementations typically print unintended characters
at the places where they are used.
Nevertheless, some manuals contain them, for example ocserv(8).
Problem reported by Kurt Jaeger <pi at FreeBSD>.
|
|
|
|
|
|
of the current user-defined macro.
This is another missing feature required for ocserv(8).
Problem reported by Kurt Jaeger <pi at FreeBSD>.
|
|
|
|
CDIOREADTOCENTRYS;
from martijn van duren
|
|
M_BWMETER.
ok mikeb@
|
|
From Michael Reed.
|
|
|
|
requested by several
discussed with deraadt@
|
|
ok stsp@
|
|
ok stsp jmc
|
|
|
|
into a common pattern. In the man page clarify the usage of the
returned route.
OK mpi@ mikeb@ jmc@
|
|
Built with gen_ctype_utf8.pl
ok stsp@
|
|
This does require perl 5.22 which is not yet in base, but it also doesn't need
to be run except when new unicode versions are released which shouldn't happen
until after perl is updated.
OK and prodding from stsp@
|
|
flags in the disklabel. These flags were discarded in 2006.
Remove documentation for and instances of 'ty'. Add instances of
'dt' that were missing. Use 'floppy' as the value of 'dt' for all
floppies and 'rdroot' for all boot images/miniroots.
Add 'rdroot' to dktypenames and an associated #define DTYPE_RDROOT,
since 'dt' values are parsed by matching entries in dktypenames[].
Slightly tweaked part of larger cleanup diff previously ok deraadt@.
|
|
from crypto libraries. Some smtp servers, notably gmail, now fail
to deliver mail to servers using DSA keys. Examples adapted from
the smtpd.conf manual. OK jmc@
|
|
ok mpi@ claudio@
|
|
|
|
with r1.18. 'rm' and 'il' were removed from getdiskbyname() in 2009
with r1.19. The associated disklabel fields were recycled for other
purposes.
Another 'harmless' part of the larger disklabel cleanup diff.
ok deraadt@ as part of that larger diff.
|
|
...although this create a race condition pointed by sthen@ where the
other side might try to negotiave IPv6 before it is enable.
This is *another* fallback of the no IPv6 by default policy. Since
setting an address implicitly brings the underlying interface UP.
And pppoe(4) (which is special) starts singing as soon as it is UP
even if no proto or parent device has been specified. Obviously this
cannot work.
Better have a working and racy example than a non-working one.
Diff submitted by Delan Azabani, thanks!
ok naddy@
|
|
|
|
|
|
ok mpi@
|
|
from clemens goessnitzer
|
|
help/ok schwarze
|
|
little lies: you have to use carpdev now to configure a carp parent
interface.
ok mpi@ jmc@
|
|
|
|
|
|
fix that now;
ok deraadt
|
|
ok deraadt
|
|
returned by AUDIO_GETxOFFS and AUDIO_xERROR ioctls.
ok deraadt
|
|
|
|
support to make it clear that pppoe(4) does work with IPv6. Problem noted
by Simon Farnsworth. Add xrefs to pppoe(4) and pppx(4) to show that this
isn't the only PPP implementation on OpenBSD. ok/tweak stsp@
|
|
ok jmc@
|
|
|
|
need a list of changes!)
|
|
(two) local changes.
|
|
|
