From: Johannes Berg <johannes@sipsolutions.net>
To: Devin Wittmayer <lucid_duck@justthetip.ca>
Cc: Alexander Wetzel <Alexander@wetzel-home.de>,
Felix Fietkau <nbd@nbd.name>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless] wifi: mac80211: drop the monitor filter counts on stop, not just sometimes
Date: Fri, 04 Sep 2026 09:49:42 +0200 [thread overview]
Message-ID: <8019b79321a8c846f5a4232c2f7fed778c0a1cc7.camel@sipsolutions.net> (raw)
In-Reply-To: <20260825043754.66918-1-lucid_duck@justthetip.ca>
On Mon, 2026-08-24 at 21:37 -0700, Devin Wittmayer wrote:
> Bringing a monitor up raises the filter counts that track what userspace
> asked to see: frames that failed their checksum, control frames, other-BSS
> traffic. Taking it down again should lower them.
Seems legit, but ...
> The rise happens for every monitor. The fall sits inside the branch that
> retires the virtual monitor, so it is skipped for an active monitor, and
> on any driver setting NO_VIRTUAL_MONITOR. For those, every up and down
> leaves another increment behind.
>
> So once anything has asked to see frames that failed their checksum, the
> hardware keeps handing them up long afterwards, to monitors that never
> asked for them. The other counts accumulate the same way, including the
> one that keeps TX status reporting armed once it has been used.
>
> Changing the flags on a running monitor still balances, so the
> accumulation boils down to the open and stop pair.
>
> Reproduced on mac80211_hwsim: an active monitor brought up and down
> leaves one unmatched increment behind, while a passive monitor on the
> same phy balances.
>
> The two sides matched until cooked monitor support was taken off the
> heat. The decrement got baked into the new conditional along with the
> virtual monitor bookkeeping and never came back out. Move it out again
> so it mirrors the increment.
Ugh. Please rewrite this manually to not just be LLM fluff, to be
something one can actually consume at human speed.
johannes
prev parent reply other threads:[~2026-09-04 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 4:37 Devin Wittmayer
2026-09-04 7:49 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8019b79321a8c846f5a4232c2f7fed778c0a1cc7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Alexander@wetzel-home.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=nbd@nbd.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®