From: Kalle Valo <kvalo@kernel.org>
To: Chenming Huang <quic_chenhuan@quicinc.com>
Cc: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH][RESEND] wifi: cfg80211: Do not create BSS entries for unsupported channels
Date: Mon, 23 Sep 2024 10:29:19 +0300 [thread overview]
Message-ID: <87h6a6akvk.fsf@kernel.org> (raw)
In-Reply-To: <20240923021644.12885-1-quic_chenhuan@quicinc.com> (Chenming Huang's message of "Mon, 23 Sep 2024 07:46:44 +0530")
Chenming Huang <quic_chenhuan@quicinc.com> writes:
> Currently, in cfg80211_parse_ml_elem_sta_data(), when RNR element
> indicates a BSS that operates in a channel that current regulatory
> domain doesn't support, a NULL value is returned by
> ieee80211_get_channel_khz() and assigned to this BSS entry's channel
> field. Later in cfg80211_inform_single_bss_data(), the reported
> BSS entry's channel will be wrongly overridden by transmitted BSS's.
> This could result in connection failure that when wpa_supplicant
> tries to select this reported BSS entry while it actually resides in
> an unsupported channel.
>
> Since this channel is not supported, it is reasonable to skip such
> entries instead of reporting wrong information.
>
> Signed-off-by: Chenming Huang <quic_chenhuan@quicinc.com>
The list of changes from v1 missing. I guess you added the 'wifi:' prefix
but did you change something else?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-09-23 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 2:16 [PATCH][RESEND] wifi: cfg80211: Do not create BSS entries for unsupported channels Chenming Huang
2024-09-23 7:29 ` Kalle Valo [this message]
2024-09-23 7:34 ` Chenming Huang
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=87h6a6akvk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_chenhuan@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