Linux wireless drivers development
 help / color / mirror / Atom feed
From: Rory Little <roryl@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
	Dylan Eskew <dylan.eskew@candelatech.com>
Subject: Re: [PATCH wireless-next v2] net: cfg80211: validate monitor channel set against radio usage
Date: Mon, 21 Sep 2026 13:55:50 -0700	[thread overview]
Message-ID: <af8ee959-a35e-4bd3-ab34-7836f1517fca@candelatech.com> (raw)
In-Reply-To: <63e5e755ce0b8390864f36c9e2eb74cf5749b5e7.camel@sipsolutions.net>

On 9/21/26 13:20, Johannes Berg wrote:
> On Mon, 2026-09-21 at 13:17 -0700, Rory Little wrote:
>>>> - Handle error return from cfg80211_get_radio_idx_by_chan
>>> Yes, but did you do it correctly? I don't think so?
>> You mean propagating -EINVAL out to the caller, right? I'd need to
>> handle the n_radio == 0 case to keep the -EBUSY behavior consistent.
> Yeah, I get that, but it seemed tgo me it should return true (accepting
> the channel change) - but then again maybe not, since it already accepts
> "only have monitors", and then getting there means there's something
> else ... sorry.

Yeah, if we are there then there are other interfaces up, so rejecting 
at that point keeps the existing behavior. I'll add a comment clarifying 
that.

On a different note, I also noticed that this introduced an issue - 
cfg80211_has_monitors_only also verifies that there is at least one 
active interface. This patch loses that verification for multi-radio 
wiphys. I will fix this in v3.

- Rory

  reply	other threads:[~2026-09-21 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 17:07 [PATCH wireless-next] net: cfg80211: Validate monitor channel set against radio usage Rory Little
2026-09-21  9:04 ` Johannes Berg
2026-09-21 18:46   ` [PATCH wireless-next v2] net: cfg80211: validate " Rory Little
2026-09-21 18:59     ` Johannes Berg
2026-09-21 20:17       ` Rory Little
2026-09-21 20:20         ` Johannes Berg
2026-09-21 20:55           ` Rory Little [this message]
2026-09-21 21:04     ` [PATCH wireless-next v3] wifi: " Rory Little
2026-09-21 18:46   ` [PATCH wireless-next] net: cfg80211: Validate " Rory Little
2026-09-21 12:04 ` [syzbot ci] " syzbot ci

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=af8ee959-a35e-4bd3-ab34-7836f1517fca@candelatech.com \
    --to=roryl@candelatech.com \
    --cc=dylan.eskew@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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