From: Johannes Berg <johannes@sipsolutions.net>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Vitaliy Shevtsov <v.shevtsov@mt-integration.ru>,
lvc-project@linuxtesting.org,
Michael Wu <flamingice@sourmilk.net>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org,
syzbot+2e5c1e55b9e5c28a3da7@syzkaller.appspotmail.com
Subject: Re: [lvc-project] [PATCH] wifi: nl80211: override all other flags if MONITOR_FLAG_COOK_FRAMES is set
Date: Thu, 30 Jan 2025 22:13:14 +0100 [thread overview]
Message-ID: <49fe46c6a158873cdc6593b0d5630b62a59ed059.camel@sipsolutions.net> (raw)
In-Reply-To: <fhgill32gd3ugmd23oxnyvvqqfd3feu4zv3ecrkubeyqhwnb2h@pkflwiezmsp2>
On Thu, 2025-01-30 at 22:23 +0300, Fedor Pchelkin wrote:
>
> Do you suggest rejecting to set MONITOR_FLAG_COOK_FRAMES overall?
No and yes :)
No for the context of this patch. Yes in general.
> Wouldn't it break existing userspace, especially in context of systems
> running old stable kernels where the patch is also needed?
>
> There is still some usage of this flag in hostap [1].
Theoretically, but I just commented on that here:
https://lore.kernel.org/r/a49e58998553c45953a30243ad1957c06ce6db8c.camel@sipsolutions.net
tl;dr: only ancient hostapd versions will actually _use_ it, and they
have to fall into a relatively narrow range (April 2009 - Dec 2011.)
> Or your suggestion is to explicitly reject setting MONITOR_FLAG_COOK_FRAMES
> only when it is passed combined with some other flags which it is
> incompatible with?
Yes.
> Btw, the fragment [2] says the cooked flag overrides the other ones.
> But it was written a long time ago so many things have changed I guess.
Indeed, that doesn't really make sense (certainly not any longer.)
> [1]: https://w1.fi/cgit/hostap/tree/src/drivers/driver_nl80211.c#n6209
And that was almost certainly the only user that ever existed, and can
only set the flag by itself.
johannes
next prev parent reply other threads:[~2025-01-30 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 12:34 Vitaliy Shevtsov
2025-01-30 12:36 ` Johannes Berg
2025-01-30 19:23 ` [lvc-project] " Fedor Pchelkin
2025-01-30 21:13 ` Johannes Berg [this message]
2025-02-03 10:40 ` Jouni Malinen
2025-02-03 10:55 ` 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=49fe46c6a158873cdc6593b0d5630b62a59ed059.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=syzbot+2e5c1e55b9e5c28a3da7@syzkaller.appspotmail.com \
--cc=v.shevtsov@mt-integration.ru \
/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®