Age | Commit message (Collapse) | Author |
|
is resolved and libpthread can be fixed.
discussed with guenther@
|
|
the bottom is reached, from Stephen Hicks.
|
|
'[1 - 0] [1]' can no longer return '1'.
Issue reported by Alexi Malinin via bugs@. Thanks!
|
|
changes by schwarze to vfprintf.c r1.71. Cherrypicked from android:
https://github.com/aosp-mirror/platform_bionic/commit/5305a4d4a723b06494b93f2df81733b83a0c46d3
ok millert
|
|
ok tom@
|
|
even layouts and to add a -E flag to select-layout to spread out cells
evenly without changing parent cells.
|
|
characters (previously they were not accounted for).
|
|
not enough room to draw it, just leave it out.
|
|
ok bluhm@, >8k makes sense claudio@
|
|
ok visa@ as part of a larger diff, ok mpi@
|
|
One step needed to completely remove ethernet-in-IP support from gif(4).
No functional changes.
ok visa@ as part of a larger diff, ok mpi@
|
|
The INET6 entries are not needed, not documented (use net.inet.etherip)
and do not appear in sysctl(8) output.
ok mpi@
|
|
able to disable OCSP without restarting iked.
ok beck@ sthen@
|
|
|
|
|
|
ok kettenis@ mpi@
|
|
OK benno, sthen
|
|
|
|
just returning failure, making them consistent with the others that
were already like that.
|
|
no functional change, ie, the output is the same
|
|
with tweaks from carlos cardenas and visa@
ok mpi@
|
|
shouldn't be fatal to the process, just the request. Reported by
Ron Frederick
|
|
bug reported and fix tested by Leonardo Guardati
OK bluhm@
|
|
|
|
|
|
/dev/arandom any longer. ok deraadt@
|
|
by such misconfigured DHCP servers.
Original diff from and ok krw@, ok sthen@
|
|
In particular, this allows SIOCGIF* requests to run in parallel.
lots of help & ok mpi, ok visa, sashan
|
|
|
|
messages. Splassert was triggered by regress/sys/netinet6/frag6.
OK mpi@ sashan@ visa@
|
|
so that statically initialized locks get properly enrolled
to the validator.
OK mpi@
|
|
OK mikeb@
|
|
due to power failure and an announcement is transmitted as input by the device
making it detectable. At this point, the device must be re-enabled to continue
working since any configuration done prior to the reset is lost.
Detection is implemented using a watchdog and enabled for all protocols. So far,
the announcement has been observed on Synaptics by me and on Elantech v4 by
bru@. Extra care has been taken to handle potential false positives: when the
announcement byte sequence is part of a valid input packet.
with help and ok bru@, mpi@
|
|
ok bru@, mpi@ (as part of a larger diff)
|
|
ok deraadt@, mpi@
|
|
ok guenther@
|
|
ok bluhm@, visa@
|
|
Pointed out by Mark Johnston, Markj@FreeBSD
|
|
back it out until i can figure the problem out.
|
|
the code has rotted, and obviously hasnt been used for ages. it is
also hard to make mpsafe. if we need something like this again it
would be better to do it from scratch.
ok tedu@ visa@
|
|
this keeps the knowledge of ifq locking in ifq.c
ok visa@
|
|
without providing a full connection specification (sshd -T -C ...)
spotted by bluhm@
|
|
this replaces ifq_start with code that waits until at least 4 packets
have been queued on the ifq before calling the drivers start routine.
if less than 4 packets get queued, the start routine is called from
a task in a softnet tq.
4 packets was chosen this time based on testing sephe did in dfly
which showed no real improvement when bundling more packets. hrvoje
popovski tested this on several nics and found an improvement of
10 to 20 percent when forwarding across the board.
because some of the ifq's work could be sitting on a softnet tq,
ifq_barrier now calls taskq_barrier to guarantee any work that was
pending there has finished.
ok mpi@ visa@
|
|
taskq_barrier guarantees that any task that was running on the taskq
has finished by the time taskq_barrier returns. it is similar to
intr_barrier.
this is needed for use in ifq_barrier as part of an upcoming change.
|
|
above and enable the driver on arm64.
From Artturi Alm. Tested by Stephen Graf.
|
|
From Artturi Alm. Tested by Stephen Graf.
|
|
Issue reported by Alexi Malinin via bugs@. Thanks!
|
|
|
|
It isn't safe to manipulate PF_KEY sockets without KERNEL_LOCK() because
they aren't protected by the NET_LOCK().
I missed this in my previous audit and neither my tests, the regression
tests nor the IPsec performance tests exposed the problem. Hopefully I
added the right check to soassertlocked() a while back.
Found the hardway by and ok sthen@
|
|
|