From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next 1/2] wifi: mac80211: fix TPE in channel switch wrapper parsing
Date: Mon, 28 Sep 2026 18:15:18 +0200 [thread overview]
Message-ID: <6187a33f3fe4f34d30bd179f2e5c64ee98dcd6eb.camel@sipsolutions.net> (raw)
In-Reply-To: <20260928144357.2e38718bb504.I8b07b323ba83173b570bc07ed61f4130b8aff04f@changeid>
On Mon, 2026-09-28 at 14:43 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> WLAN_EID_TX_POWER_ENVELOPE is a regular (non-extended) element,
> but I accidentally used find_ext_elem() for it. Fix this.
>
> Fixes: 4540568136fe ("wifi: mac80211: handle TPE element during CSA")
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> net/mac80211/parse.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/mac80211/parse.c b/net/mac80211/parse.c
> index 3b66ca7d7a5c..4ff726eef453 100644
> --- a/net/mac80211/parse.c
> +++ b/net/mac80211/parse.c
> @@ -692,8 +692,8 @@ _ieee802_11_parse_elems_full(struct ieee80211_elems_parse_params *params,
> IEEE80211_PARSE_ERR_BAD_ELEM_SIZE;
> }
>
> - subelem = cfg80211_find_ext_elem(WLAN_EID_TX_POWER_ENVELOPE,
> - pos, elen);
> + subelem = cfg80211_find_elem(WLAN_EID_TX_POWER_ENVELOPE,
> + pos, elen);
Actually, this should also be a loop.
johannes
prev parent reply other threads:[~2026-09-28 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 12:43 [PATCH wireless-next 1/2] wifi: mac80211: fix TPE in channel switch wrapper parsing Johannes Berg
2026-09-28 12:43 ` [PATCH wireless-next 2/2] wifi: cfg80211: type-check (extended) element search functions Johannes Berg
2026-09-28 16:15 ` Johannes Berg [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=6187a33f3fe4f34d30bd179f2e5c64ee98dcd6eb.camel@sipsolutions.net \
--to=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