From: Johannes Berg <johannes@sipsolutions.net>
To: Louis Kotze <loukot@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: nl80211: say why the association BSS lookup failed
Date: Tue, 21 Jul 2026 17:31:43 +0200 [thread overview]
Message-ID: <2629d83dd460f3d9a60566f3fad975db13b045c3.camel@sipsolutions.net> (raw)
In-Reply-To: <20260711043432.2767225-1-loukot@gmail.com>
On Sat, 2026-07-11 at 06:34 +0200, Louis Kotze wrote:
>
> +/* why __cfg80211_get_bss() found no usable BSS entry */
> +#define CFG80211_BSS_MISS_EXPIRED BIT(0)
> +#define CFG80211_BSS_MISS_USE_FOR BIT(1)
> +
> +u32 cfg80211_get_bss_miss_reasons(struct wiphy *wiphy,
> + struct ieee80211_channel *channel,
> + const u8 *bssid,
> + const u8 *ssid, size_t ssid_len,
> + enum ieee80211_bss_type bss_type,
> + enum ieee80211_privacy privacy,
> + u32 use_for);
This seems ... messy, and also racy? I really don't like it, so you're
going to have to work extra hard to convince me of it.
> @@ -13068,8 +13073,23 @@ static struct cfg80211_bss *nl80211_assoc_bss(struct cfg80211_registered_device
> IEEE80211_BSS_TYPE_ESS,
> IEEE80211_PRIVACY_ANY,
> use_for);
can't we just pass the info (or NULL) to __cfg80211_get_bss() directly
and have that fill the right problem message there? There aren't even
any callers to it outside of cfg80211, and cfg80211_get_bss() can just
pass NULL.
johannes
next prev parent reply other threads:[~2026-07-21 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 4:34 Louis Kotze
2026-07-21 15:31 ` Johannes Berg [this message]
2026-07-21 18:11 ` [PATCH v2 0/2] wifi: cfg80211: say why the auth/assoc " Louis Kotze
2026-07-21 18:11 ` [PATCH v2 1/2] " Louis Kotze
2026-07-21 22:10 ` Johannes Berg
2026-07-22 7:07 ` Louis Kotze
2026-07-22 7:07 ` [PATCH v3 0/2] " Louis Kotze
2026-07-22 7:07 ` [PATCH v3 1/2] " Louis Kotze
2026-07-22 7:07 ` [PATCH v3 2/2] wifi: cfg80211: tests: check BSS lookup failure reasons Louis Kotze
2026-07-21 18:11 ` [PATCH v2 " Louis Kotze
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=2629d83dd460f3d9a60566f3fad975db13b045c3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loukot@gmail.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
all inboxes | Powered by JetHome®