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.
