| Commit message (Collapse) | Author | Files | Lines |
|
|
|
(If anyone needs a bit more handholding than is in release(8), the faq page
https://www.openbsd.org/faq/faq5.html#Release has more information about
setting this up).
Much simplified from, but inspired by, various diffs from ians@. ok tb@ jmc@
|
|
|
|
|
|
have now.
as seen by landry@
|
|
that doesn't exist.
|
|
|
|
exchange that we initiatiated, we are not allowed to respond to such
a msg. Also we don't need the DH check in ikev2_sa_initiator_dh() as
it's only called when we initiate, so the check would not run, or when
we get a Create Child SA response, where an error should only lead to
us having another attempt at an exchange.
Found by and ok markus@
|
|
Now that we call rasops_putchar_rotated(), we don't need ri anymore.
OK kettenis@
|
|
remove exsysreg(4). The exsysreg(4) driver would no longer attach
as syscon(4) would match its node in the device tree. As a result the
driver corss-call would panic.
Makes te Odroid-XU4 work again.
|
|
|
|
|
|
|
|
|
|
OK jmc@ tb@
|
|
|
|
|
|
helped to find out if the default route was configured by dhclient.
Check if the interface connected to the default route is in the
dhcp interface group which accomplishes the same functionality.
With feedback from and OK krw@
|
|
interrupts in the lookup table. On machines like the Oracle T7-2 this
would make the code believe that there is interrupt sharing, but since
we bypass intr_list_handler() when using the cookie-based interrupt API,
we wouldn't properly acknowledge the interrupt.
This fixes the last remaining problem with interrupts on the Oracle T7-2.
|
|
setup.
|
|
from Charles Howard in GitHub issue 1161.
|
|
|
|
|
|
respectively to avoid compilation errors when one of the POSIX or
X/OPEN version macros is defined. Also sync the field descriptions
with kqueue.2. OK deraadt@
|
|
|
|
|
|
that 'send host-name' is the default behaviour for
dhclient.
ok rpe@
|
|
Using if_enqueue() here, from interrupt context, might result in
the packet beeing enqueued, incorrectly encrypted, on the TX ring.
This race has been recently exposed by the re-introduction of the
TX mitigation. It exists because the net80211 stack sets
IEEE80211_NODE_TXPROT on the node while processing the 3rd message,
assuming the answer has already been transmitted. However a CPU
returns from if_enqueue() it cannot assume that the send queue is
empty. So call if_start() to flush this queue.
Encrypting the 4th message of the 4way handshake with the new key
breaks WPA handshake as found the hardway by anton@.
Race analysed by dlg@, a lot of net80211 inputs and suggetions from
stsp@.
ok stsp@, dlg@
|
|
From Claus Assmann with minor tweaks by me.
ok millert
|
|
ok deraadt
|
|
|
|
|
|
ok zhuk@ deraadt@
|
|
|
|
move rxfill in ixl_up so the qtail is only written once.
|
|
|
|
for now we still only have one set of tx and rx rings, but sets us up to
bump that number.
|
|
|
|
|
|
deliberately does not save the floating-point argument registers
before calling _dl_bind(). Doing so would force an FPU context switch
upon every function call through the PLT. But since we compile ld.so
with -march=armv8-a+nofp+nosimd this is safe since nothing in the _dl_bind()
codepath uses he FPU registers.
ok guenther@, drahn@
|
|
too much software generates inconsistent messages, so we need a
better plan.
|
|
environment variable.
|
|
six letters if they actually match "--- a/" and "+++ b/" instead of
laxer checks.
ok tom, tedu, millert
|
|
for it. Removes the need to install a dhclient.conf for a default
configuration.
Install script simplification to follow.
General enthusiasm. ok millert@ benno@ tom@ ian@
|
|
1) Use only one antenna while scanning on 5GHz. Fixes very low RSSI values.
2) During a background scan while associated to a 5GHz AP, send probe
requests on 2GHz channels with an OFDM rate (6Mbps) because the buggy
firmware does not like sending with a CCK rate (1Mbps) in this state.
CCK rates are not valid for 5GHz, which could explain this firmware bug.
Taken from FreeBSD r222679.
jca@ tested and confirmed the first problem but lacks a 5GHz access point to
associate to and test the second one with.
I am going to *blindly trust* FreeBSD on the second one! It is not a big deal
if it doesn't actually apply to our firmware version as the change itself is
rather inconsequential in practice. And 4965 hardware is quite rare nowadays.
ok jca@
|
|
ok kettenis@
|
|
This is a step towards MI mutexes.
ok kettenis@
|
|
assembled into a volume, to enure the on-disk
metadata and the in-memory metadata agree.
|
|
With support from guenther@ and millert@; final okay espie@
|
|
cannot be calculated from the CPUID register, because the CPU does not
support it, but can be calibrated from another timer, the vmm(4) guest
doesn't have a chance to read or calibrate its own TSC frequency since
it has no access to a precise enough time counter. In that case, fake
the existence of the register and supply our calibrated TSC frequency.
mlarkin@ tells me this also greatly helps Linux guests.
ok mlarkin@
|