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] wifi: mac80211: Guard FILS discovery and unsolicited broadcast probe response
Date: Thu, 10 Sep 2026 13:14:00 +0530	[thread overview]
Message-ID: <ff91a2e3-fd29-46b8-ba63-7cfe0f8c8e26@oss.qualcomm.com> (raw)
In-Reply-To: <63ab746686edee2e7919edb1cf6c5ce06e9999d0.camel@sipsolutions.net>



On 9/4/2026 3:46 PM, Johannes Berg wrote:
> On Thu, 2026-08-20 at 21:37 +0530, Manish Dharanenthiran wrote:
>>
>> +++ b/net/mac80211/cfg.c
>> @@ -1138,7 +1138,7 @@ static int ieee80211_set_fils_discovery(struct ieee80211_sub_if_data *sdata,
>>   	struct fils_discovery_data *new, *old = NULL;
>>   	struct ieee80211_fils_discovery *fd;
>>   
>> -	if (!params->update)
>> +	if (!params->update || link_conf->nontransmitted)
>>   		return 0;
> 
> So why shouldn't we just reject it?
>   

Currently in user-space there is no restriction on sending this for 
non-transmitting BSS, thus it may send this for those BSSs as well, 
however the driver will use only for Tx BSS and ignore this config for 
Non-Tx BSS. Returning an error here could be fatal because failing 
start_ap or update_ap operation would result in failure of bringing up 
those BSSs.

We are working on the patch to update the behavior in hostap as well to 
not set this for Non-Tx BSS, but to maintain the backward compatibility, 
and the update from any other user-space application thus doesn't handle 
in a similar way, we ignored the update silently and kept as no-op.

Please let us know your thoughts.

>>   	fd = &link_conf->fils_discovery;
>> @@ -1173,7 +1173,7 @@ ieee80211_set_unsol_bcast_probe_resp(struct ieee80211_sub_if_data *sdata,
>>   {
>>   	struct unsol_bcast_probe_resp_data *new, *old = NULL;
>>   
>> -	if (!params->update)
>> +	if (!params->update || link_conf->nontransmitted)
>>   		return 0;
> 
> Same here.
> 
> johannes

-- 
- Manish D


  reply	other threads:[~2026-09-10  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 16:07 [PATCH wireless-next] wifi: mac80211: Guard FILS discovery and unsolicited broadcast probe response Manish Dharanenthiran
2026-09-04 10:16 ` Johannes Berg
2026-09-10  7:44   ` Manish Dharanenthiran [this message]
2026-09-10  8:10     ` Johannes Berg
2026-09-10 10:04       ` Manish Dharanenthiran

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=ff91a2e3-fd29-46b8-ba63-7cfe0f8c8e26@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