Linux wireless drivers development
 help / color / mirror / Atom feed
From: Manish Dharanenthiran <manish.dharanenthiran@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next v2] wifi: mac80211: Guard FILS discovery and unsolicited broadcast probe response
Date: Mon, 21 Sep 2026 21:16:02 +0530	[thread overview]
Message-ID: <c09e2ee9-f034-46a2-b185-e37e492dfc3b@oss.qualcomm.com> (raw)
In-Reply-To: <a1a5fa095dabb37ef67137bf1fb3ce2eb7e8d84e.camel@sipsolutions.net>



On 9/21/2026 2:27 PM, Johannes Berg wrote:
> On Fri, 2026-09-18 at 12:47 +0530, Manish Dharanenthiran wrote:
>>
>> Currently in user-space there is no restriction on sending this for
>> non-transmitting BSS, thus it may send these for those BSSs as well.
>> However the driver will use the config only for transmitting BSS and
>> ignore for non-transmitting BSS. Returning an error here, even if
>> user-space sets these, could be fatal because failing start_ap or
>> update_ap operation would result in failure of bringing up those BSSs.
>> Thus, ignore the config for non-transmitting BSS silently.
> 
> And honestly, it really _should_ be fatal since it really is a wront
> configuration, so that text isn't really that useful, nor the comments:
> 
>> +	/*
>> +	 * Only transmitting BSS should set this config, ignore this config for
>> +	 * non-transmitting BSS silently even if user-space sets it, as
>> +	 * returning error would result in failure of bringing up of those BSSs.
>> +	 */
>> +	if (!params->update || link_conf->nontransmitted)
> 
> Please state that currently it actually _is_ (erroneously) being set by
> hostapd and we need to keep it working.
> 
> johannes

Understood!, will modify the text and the comments in the next version.

-- 
- Manish D


      reply	other threads:[~2026-09-21 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  7:17 [PATCH wireless-next v2] wifi: mac80211: Guard FILS discovery and unsolicited broadcast probe response Manish Dharanenthiran
2026-09-21  8:57 ` Johannes Berg
2026-09-21 15:46   ` Manish Dharanenthiran [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=c09e2ee9-f034-46a2-b185-e37e492dfc3b@oss.qualcomm.com \
    --to=manish.dharanenthiran@oss.qualcomm.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