public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Alexey Berezhok <a@bayrepo.ru>,
	Arend van Spriel <aspriel@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@kernel.org>,
	linux-wireless@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] wifi: brcmfmac: do not cast hidden SSID attribute value to boolean
Date: Thu, 8 Feb 2024 15:06:32 +0100	[thread overview]
Message-ID: <1bc49c2a-1f62-4801-90c3-048b27f6475c@broadcom.com> (raw)
In-Reply-To: <20240208085121.2430-1-a@bayrepo.ru>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On 2/8/2024 9:51 AM, Alexey Berezhok wrote:
> In 'brcmf_cfg80211_start_ap()', not assume that
> NL80211_HIDDEN_SSID_NOT_IN_USE is zero but prefer
> an explicit check instead. Compile tested only.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.

Thanks, Alexey

Makes sense, but ....

> Signed-off-by: Alexey Berezhok <a@bayrepo.ru>
> ---
>   drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> index 736b2ada6..63f6e9436 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> @@ -5272,7 +5272,7 @@ brcmf_cfg80211_start_ap(struct wiphy *wiphy, struct net_device *ndev,
>   					      settings->hidden_ssid);

settings->hidden_ssid has already been used above in following call:

		err = brcmf_fil_iovar_int_set(ifp, "closednet",
					      settings->hidden_ssid);

So we pass the value as is to firmware using the same assumption, ie. 
NL80211_HIDDEN_SSID_NOT_IN_USE. Is this not ABI thus very unlikely to 
change?

@Johannes:
Actually not quite understanding the reason for having this setting in 
nl80211. hidden_ssid means SSID element length is zero, right?

Regards,
Arend

>   		if (err) {
>   			bphy_err(drvr, "%s closednet error (%d)\n",
> -				 settings->hidden_ssid ?
> +				 (settings->hidden_ssid != NL80211_HIDDEN_SSID_NOT_IN_USE) ?
>   				 "enabled" : "disabled",
>   				 err);
>   			goto exit;

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]

  reply	other threads:[~2024-02-08 14:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08  8:51 [PATCH] wifi: brcmfmac: do not cast hidden SSID attribute value to boolean Alexey Berezhok
2024-02-08 14:06 ` Arend van Spriel [this message]
2024-02-08 14:15   ` Johannes Berg
2024-02-08 15:56     ` Arend Van Spriel
2024-02-12 15:38 ` Kalle Valo
2024-02-12 16:00   ` Arend van Spriel
2024-02-12 16:03     ` Kalle Valo
2024-02-12 16:43       ` Arend Van Spriel
2024-02-13 13:34         ` Kalle Valo
2024-02-13 14:01           ` Arend van Spriel
2024-02-13 15:46             ` Kalle Valo
2024-02-13 17:40               ` Arend Van Spriel
2024-02-14 10:28     ` Alexey Berezhok
2024-02-14 11:44       ` Arend Van Spriel
2024-02-19 18:25 ` andy.shevchenko

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=1bc49c2a-1f62-4801-90c3-048b27f6475c@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=a@bayrepo.ru \
    --cc=aspriel@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lvc-project@linuxtesting.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