OpenBSD cvs log

created 2024-05-10T00:57:15Z
begin 2024-05-08T00:00:00Z
end 2024-05-09T00:00:00Z
path src/sys
commits 6

date 2024-05-08T13:01:30Z
author bluhm
files src/sys/netinet/ip_input.c log diff annotate
src/sys/netinet6/ip6_input.c log diff annotate
message Fix route leak in ip input.

In previous commit when refactoring the route cache, a rtfree() has
been forgotten. For each forwarded packet the reference counter
of the route entry was increased. This eventually leads to an
integer overflow and triggers kassert.

reported by and OK jan@

date 2024-05-08T13:05:33Z
author claudio
files src/sys/kern/kern_sig.c log diff annotate
message Rework how action SIG_HOLD is handled in ptsignal.

Since we want to unlock sigsuspend, ptsignal needs to double check in the
SSLEEP case that the signal being delivered is still masked or unmasked.
Remove the early return for action SIG_HOLD so that the SSLEEP case can
properly recheck the sigmask.

On top of this update siglist only in one place at the end of ptsignal
this now includes the clearing of signals for the SA_CONT and SA_STOP
cases.

OK mpi@

date 2024-05-08T14:02:59Z
author stsp
files src/sys/net80211/ieee80211_output.c log diff annotate
message disable the regular ieee80211_encap() Tx path in monitor mode

Frames injected from user space carry the DLT_IEEE802_11_RADIO
mbuf tag, and are handled as a special case. Do not fall back
to regular encapsulation while we are in monitor mode and the
frame injected by userspace is found to be invalid.

This fixes an issue when iwx(4) runs in monitor mode with addresses
configured on the interface and leaving 11n/11ac mode directly for
monitor mode. In this case, traffic generated by userspace or the
kernel (such as ICMPv6) would trigger Tx attempts, which in turn
would trigger an attempt to set up a block ACK agreement and then
cause a firmware panic.

This points at a related issue where interface configuration state
is not properly cleaned up while switching into monitor mode.
The 11n/11ac interface config should ideally be cleared completely,
preventing block ack from being initiated.

But preventing the stack from trying to send frames down the regular
Tx path in monitor mode is a good idea in general because drivers may
not handle this very well for various reasons, block ack being just one.

tested by jmc@ and myself on iwx ax200

date 2024-05-08T14:03:54Z
author stsp
files src/sys/dev/pci/if_iwx.c log diff annotate
src/sys/dev/pci/if_iwxreg.h log diff annotate
message fix iwx(4) monitor mode

Monitor mode was broken by a recent firmware update. Two tweaks make
it work again:

1) The firmware does not like us sending the power-mode command while
in monitor mode and will panic, so simply don't do that.

2) We no longer add two queues while in monitor mode, just one queue
for frame injection. This queue's index will be 1, not 2. Make the
driver expect the correct index to prevent an error when monitor mode
is entered.

tested by jmc@ and myself on iwx ax200

date 2024-05-08T17:52:11Z
author jan
files src/sys/dev/pci/if_ixl.c log diff annotate
message ixl(4): force mss of tso packets in hardware supported range.

ok bluhm@

date 2024-05-08T18:00:55Z
author guenther
files src/sys/arch/amd64/amd64/cacheinfo.c log diff annotate
message Suppress cache-info dmesg lines when they are identical to the
previous cpu.

testing on hybrid box by jmatthew@
suggestions from kettenis@
ok deraadt@