From: Johannes Berg <johannes@sipsolutions.net>
To: Zhiling Zou <zhilinz@nebusec.ai>, linux-wireless@vger.kernel.org
Cc: michal.kazior@tieto.com, vega@nebusec.ai
Subject: Re: [PATCH wireless 0/1] wifi: mac80211: keep paired old chanctx alive
Date: Mon, 03 Aug 2026 10:40:22 +0200 [thread overview]
Message-ID: <4cd5a1c8e807d064714a2f6fed46ea49d1033ace.camel@sipsolutions.net> (raw)
In-Reply-To: <cover.1785730815.git.zhilinz@nebusec.ai> (sfid-20260803_063526_248734_4BF193C7)
Hi,
FWIW, none of your mails seem to be reaching the mailing list - I have
emails sent after yours on it, so I don't think it's just a delay.
> We found and validated a issue in net/mac80211/chan.c. The bug is reachable by a
> non-root user via user and net namespace.
With all these hwsim bugs I wonder - how do you get it loaded in the
first place? I don't think it's very interesting if (real, non-ns) root
has to load it first, basically nobody _really_ has much interest in it
other than while testing/developing, and even then it'll mostly get used
in VMs. I guess you could technically trigger this on real HW in a
namespace, but ... again that needs real root to put it there.
Not saying that makes it completely irrelevant, but all the whole "bug
is reachable by non-root ..." seems to significantly overstate it?
johannes
next prev parent reply other threads:[~2026-08-03 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 4:35 [PATCH wireless 0/1] wifi: mac80211: keep paired old chanctx alive Zhiling Zou
2026-08-03 4:35 ` [PATCH wireless 1/1] " Zhiling Zou
2026-08-03 8:40 ` Johannes Berg [this message]
2026-08-03 10:01 ` [PATCH wireless 0/1] " Johannes Berg
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=4cd5a1c8e807d064714a2f6fed46ea49d1033ace.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=vega@nebusec.ai \
--cc=zhilinz@nebusec.ai \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.