| Age | Commit message (Collapse) | Author |
|---|
|
from a USB serial number, as recommended by the umass spec.
ok dlg@
|
|
be free()ed, iterate over the file_list, and find the structure
to free. This is safer and simpler. No behaviour change
|
|
|
|
More HISTORY.
Using feedback from jmc@.
"I think that is correct.
If it isn't, someone out there will eventually moan :)" deraadt@
|
|
protocol specific code. No behaviour change
|
|
return value, not a size_t which does not grok -1.
ok matthew@
|
|
until they're zombies and then send them signals (for intr mounts). Until
that is untangled, the sigacts change is unsafe. sthen@ was the victim
for this one
|
|
ucfirst(), uc() and lc() forget to set the tainted flag if input
was marked as tainted.
http://rt.perl.org/rt3/Public/Bug/Display.html?id=87336
http://perl5.git.perl.org/perl.git/commitdiff/539689e74a3bcb04d29e4cd9396de91a81045b99
ok millert@
|
|
Rather then rewriting history, I've chosen to erase it; as it
contains only pointless trivia...
ok deraadt@
|
|
mouse-select-pane.
|
|
|
|
ok espie@
|
|
clicking on the status line, written by hsim at gmx dot li.
|
|
The problems during the hackathon were not caused by this (most likely).
prodded by deraadt@ and beck@
|
|
|
|
asked by/ok deraadt@, ajacoutot@
|
|
ok millert@
|
|
In effect, this removes the "old" vndX nodes, and renames
the svndX nodes to vndX.
Old svndX nodes will still continue to work though, for now.
Cleanup accordingly.
ok deraadt@, todd@
comments and ok on the man page bits from jmc@
|
|
this will treat vndX the same as svndX.
ok and gcc2 fixes from deraadt@
|
|
Not %d or %u. May help some of the issues reported by Richard Toohey.
Tested by Steven R. Gerber.
|
|
picks the peer from the acquire message and allows to match masked
peers in the policies like "peer any" or "peer 10.0.0.0/8" instead of
requiring exactly matching peer specifications.
ok mikeb@
|
|
matching policy and init a new IKE SA. This adds support for "acquire mode"
from static flows.
ok mikeb@
|
|
tested in bulk build.
ok millert@
|
|
occurence.
with a small tweak from an ok sthen@
|
|
when leaving. when you're handling an interrupt it is masked.
whacking the chip is work for no gain.
modify the interrupt handler so it only processes the rings once
rather than looping over them until it runs out of work to do
looping in the isr is bad for several reasons:
firstly, the chip does interrupt mitigation so you have a
decent/predictable amount of work to do in the isr. your first loop
will do that chunk of work (ie, it pulls off 50ish packets), and
then the successive looping aggressively pull one or two packets
off the rx ring. these extra loops work against the benefit that
interrupt mitigation provides.
bus space reads are slow. we should avoid doing them where possible
(but we should always do them when necessary).
doing the loop 5 times per isr works against the mclgeti semantics.
it knows a nic is busy and therefore needs more rx descriptors by
watching to see when the nic uses all of its descriptors between
interrupts. if we're aggressively pulling packets off by looping
in the isr then we're skewing this check.
ok deraadt@
|
|
eject events, then the ppb's interrupt handler can be run at IPL_BIO.
This makes a huge difference on modern server with mpi/bge/bnx.
In snapshots for about 2 weeks now...
|
|
this probably means the controller is dead -- as in, a hot plug eject
event. in that case, mark the driver dead and try harder to return -1
in the interrupt handler.
tested by many
ok dlg, miod did not object
|
|
|
|
name (though we don't actually enforce this at present). Move one up
that was out of sequence
|
|
|
|
|
|
|
|
attaching since theyre useless without mpath.
the path drivers ask mpath if its ok to use the device before doing their
own matches (this is so mpath can prevent paths attaching to itself), so
im just adding this check there.
this uses code from miod to walk cfdata for the mpath entry and then checks
its state. this is ok because mpath is only attached in one place, so there
arent multiple cfdata entries for it.
ok krw@ deraadt@ miod@ matthew@
|
|
its listener socket and refuse future multiplexing requests; ok markus@
|
|
deraadt@ suggests to remove the old file right away.
|
|
|
|
to the new Perl script /usr/libexec/security.
The new script was tested by sthen@ and ajacoutot@.
Committing now due to repeated prodding from deraadt@.
In case problems show up, they will be fixed in tree.
|
|
|
|
by deraadt@.
|
|
/etc/fstab, after asking user. Current default is existing behaviour.
Feedback & suggestions deraadt@, halex@, jsing@, todd@.
ok deraadt@
|
|
test it now that it's in-tree. ok deraadt ("It causes no harm")
|
|
addresses from process context by scheduling a work queue.
Fixes an assertwaitok panic. ok henning
|
|
|
|
ok deraadt
|
|
off anymore.
ok miod
|
|
as noted by schwarze@, the semantics of the .Bk macro is slightly
different now to conform with modern groff releases; using a
command-line option (.Op) macro, instead of its multiline version,
while preserving the .Bk/.Ek block makes our manual pages compatible
with mandoc, new groff and even groff-1.15.
ok jmc@, schwarze@
|
|
Suggestions from deraadt@ and jmc@.
ok jmc@
|
|
warning unless we ask dhclient to reject leases with unknown options
OK krw@
(this was lost in my tree for even longer)
|
|
hints for the proper fix, and OK claudio@
(this was lost in my tree for far too long)
|
|
|
