linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5 2/3] wifi: mac80211: add support for AP channel switch with MLO
Date: Tue, 30 Jan 2024 11:51:23 +0100	[thread overview]
Message-ID: <7e342de34398b844226ea53851cd2b081d8131ce.camel@sipsolutions.net> (raw)
In-Reply-To: <033151e5-7857-4c44-9b12-d8d8317a4139@quicinc.com>

On Sat, 2024-01-27 at 10:28 +0530, Aditya Kumar Singh wrote:
> > 
> > Hm. I'm going to send some patches soon that remove the puncturing stuff
> > and move it into the chandef (as we discussed elsewhere), but just
> > noting that - doesn't need to concern you here, I think.
> > 
> 
> Oh okay! Let's see if at all it conflicts, will send a re-based once 
> those gets merged.

I did send my patches now, so you're very much welcome to take a look at
all that I've posted (and provide comments, I'd appreciate it!), but
*please* don't rebase right now or anything, was just noting this in
passing.

If we're happy with both sets of patches surely I can also deal with the
conflicts, that will not be hard.

> > > +	if (cfg80211_chandef_identical(&params->chandef, &link_conf->chandef))
> > >   		return -EINVAL;
> > 
> > Also another thing unrelated to your patch - I'm thinking about removing
> > that identical() check entirely - you might want to switch to the same
> > channel with quiet=1. At least for testing that'd be really useful, and
> > I don't think it really serves any purpose to forbid it.
> > 
> Yeah, we can do. But is there any actual use case? Also, what if some 
> notorious user space application simply sends NL command without even 
> quiet=1? There should be some check I guess?

I did post that patch too, and we're probably better off discussing it
there, but ... I'm not sure we care much about a broken userspace
application running with root privileges breaking something here? :-)

And at least for testing it's very useful to be able to do that. Agree
that identical channel and quiet==0 doesn't make _sense_, but even then
I'm not sure there's a lot of value in not permitting it. With quiet==1
at least it does make some sense still though, and we're currently not
allowing it, hence my patch (to be able to test scenarios like that we
saw elsewhere.)

Anyway, again, don't bother about rebase or anything!

johannes

  reply	other threads:[~2024-01-30 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 13:04 [PATCH v5 0/3] wifi: cfg80211/mac80211: add link_id handling in AP channel switch during Multi-Link Operation Aditya Kumar Singh
2024-01-25 13:04 ` [PATCH v5 1/3] wifi: cfg80211: send link id in channel_switch ops Aditya Kumar Singh
2024-01-26  9:18   ` Johannes Berg
2024-01-27  4:52     ` Aditya Kumar Singh
2024-01-25 13:04 ` [PATCH v5 2/3] wifi: mac80211: add support for AP channel switch with MLO Aditya Kumar Singh
2024-01-26  9:31   ` Johannes Berg
2024-01-27  4:58     ` Aditya Kumar Singh
2024-01-30 10:51       ` Johannes Berg [this message]
2024-01-25 13:04 ` [PATCH v5 3/3] wifi: mac80211: update beacon counters per link basis Aditya Kumar Singh
2024-01-26  9:31   ` Johannes Berg
2024-01-27  5:01     ` Aditya Kumar Singh
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25 12:58 [PATCH 0/3] wifi: cfg80211/mac80211: add support to flush stations based on link ID Aditya Kumar Singh
2024-01-25 12:58 ` [PATCH v5 2/3] wifi: mac80211: add support for AP channel switch with MLO Aditya Kumar Singh

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=7e342de34398b844226ea53851cd2b081d8131ce.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_adisi@quicinc.com \
    /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;
as well as URLs for NNTP newsgroup(s).