Do not zeroize already zeroed buffer in sysctl_sysvipc(). The
KERN_SYSVIPC_SEM_INFO case was a part of the big semaphores diff,
KERN_SYSVIPC_SHM_INFO case to the next one.
ok deraadt
Implement bounce buffers for arm64. Almost identical to the riscv64
version, but for now this strips the BUS_DMA_64BIT flag since the DMA
constraints on arm64 also include bus constraints. This will be fixed
in a future diff.
(files missed in the previous commit)
Implement bounce buffers for arm64. Almost identical to the riscv64
version, but for now this strips the BUS_DMA_64BIT flag since the DMA
constraints on arm64 also include bus constraints. This will be fixed
in a future diff.
Adjust handling of limits in up_generate_addpath()
The maxpaths limit is straightforward but the handling of plus is more
sublte. If plus == 0 then no extra paths should be added. So the default
is to not include any extra paths (unless add-path send all is used).
If plus is set and mmaxpaths is 0 add up to plus additional paths.
If plus and max are used together the first limit reached will break the
loop.
OK tb@
Make qwx(4) send the PMF good-bye deauth frame when hopping out of RUN state.
In addition to sending the PMF good-bye deauth frame from qwx_stop() we
must also send it when leaving RUN state for other reasons.
Provided we are still running with IFF_RUNNING since otherwise qwx_stop()
has already sent the deauth frame. And provided the AP did not just send
a deauth frame to us, which also covers the background-scan/roaming case
where a deauth frame is sent via ieee80211_node_tx_stopped() and net80211
is faking our old AP's deauth event.
Only send the PMF good-bye deauth frame if the WPA handshake has succeeded.
If the RSN port is not marked valid then we have never exchanged keys with
our access point and sending a correctly encrypted deauth frame is impossible.
Ensure no new tasks get scheduled while IFF_RUNNING is set in qwx_stop().
This should prevent a crash I've seen happen once where the newstate task
was scheduled after an incoming auth response frame while userland was in
qwx_stop() (i.e. ifconfig qwx0 down). The newstate task then crashed
because qwx_stop() had already begun to tear down driver state.
Fix interlock between the (badly named) CRASH_FLUSH flag which prevents
new tasks, and IFF_RUNNING which indicates whether the device is ready.
qwx_stop() now clears IFF_RUNNING before the CRASH_FLUSH flag is cleared.
There was a small window in qwx_stop() where IFF_RUNNING was still set
while CRASH_FLUSH was clear again.
To make this work with PMF we need to send our good-bye deauth frame earlier
since sending management frames requires IFF_RUNNING to be set.
sys/qwz: implement regulatory domain for 2.4Ghz and 5Ghz
without regulatory domain support it uses world, and some chanells not
available from firmware point of view when AP can actually use it.
OK: mglocker@
libcrypto/ui: mechanically rename the union _ into u
While mainstream OS use compilers that understand anonymous unions, which
would be cleaner here, some special snowflakes rely on LibreSSL in their
stacks and they sometimes use very old and special compilers. There is no
need to impose a burden on them. There is far more impactful and important
cleanup that could be done in the ui pit.
This obviates jsg's upcoming removal of a windows-ce workaround.
discussed with jsing
Add peer to qwx(4) firmware after starting the vdev, not before.
From mglocker@ via qwz(4)
On ath12k this fixed a firmware crash by avoiding the peer getting
created with a half-initialized vdev. The fix does not hurt on ath11k
so apply it to qwx(4) as well.
relayd: add support for the MKCALENDAR HTTP method
relayd is missing this method from the WebDAV/CalDAV extensions. This causes
issues when using relayd as a reverse proxy in front of CalDAV servers like
Nextcloud.
OK kirill@
