From: Zong-Zhe Yang <kevin_yang@realtek.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Johannes Berg <johannes.berg@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: On 021d53a3d87e ("wifi: mac80211: fix NULL dereference at band check in starting tx ba session")
Date: Tue, 8 Apr 2025 02:28:31 +0000 [thread overview]
Message-ID: <d5b6ba0e6d0e449883ecbc062d343a75@realtek.com> (raw)
In-Reply-To: <95a01ec8-4f2e-4cc0-a107-cb40257f100e@yandex.ru>
Dmitry Antipov <dmantipov@yandex.ru> wrote:
>
> Looking at 021d53a3d87e ("wifi: mac80211: fix NULL dereference at band check in starting tx
> ba session"), can the following be useful for older (e.g. 5.10) kernels without any MLO
> support?
>
> diff --git a/net/mac80211/agg-tx.c b/net/mac80211/agg-tx.c index
> 4b4ab1961068..1a89ba2aecaa 100644
> --- a/net/mac80211/agg-tx.c
> +++ b/net/mac80211/agg-tx.c
> @@ -595,7 +595,8 @@ int ieee80211_start_tx_ba_session(struct ieee80211_sta *pubsta, u16
> tid,
> return -EINVAL;
>
> if (!pubsta->ht_cap.ht_supported &&
> - sta->sdata->vif.bss_conf.chandef.chan->band != NL80211_BAND_6GHZ)
> + !pubsta->vht_cap.vht_supported &&
> + !pubsta->he_cap.has_he)
> return -EINVAL;
>
> if (WARN_ON_ONCE(!local->ops->ampdu_action))
>
> Dmitry
>
Without MLO, no NULL dereference here, and the original logic is workable (though not very intuitive).
So, to me, it doesn't seem much necessary for older kernels.
prev parent reply other threads:[~2025-04-08 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 14:25 On 021d53a3d87e ("wifi: mac80211: fix NULL dereference at band check in starting tx ba session") Dmitry Antipov
2025-04-08 2:28 ` Zong-Zhe Yang [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=d5b6ba0e6d0e449883ecbc062d343a75@realtek.com \
--to=kevin_yang@realtek.com \
--cc=dmantipov@yandex.ru \
--cc=johannes.berg@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.