From: Remi Pommarel <repk@triplefau.lt>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless] wifi: mac80211: Fix ADDBA update when HW supports reordering
Date: Tue, 17 Feb 2026 14:05:24 +0100 [thread overview]
Message-ID: <aZRnlPA_uY9uWuKr@pilgrim> (raw)
In-Reply-To: <f1243e86eea72999581d33c6f97ff9015ce71542.camel@sipsolutions.net>
On Tue, Feb 17, 2026 at 12:30:08PM +0100, Johannes Berg wrote:
> On Tue, 2026-02-17 at 11:36 +0100, Remi Pommarel wrote:
> > Commit f89e07d4cf26 ("mac80211: agg-rx: refuse ADDBA Request with timeout
> > update") added a check to fail when ADDBA update would change the
> > timeout param.
> >
> > This param is kept in tid_ampdu_rx context which is only allocated on HW
> > that do not set SUPPORTS_REORDERING_BUFFER. Because the timeout check
> > was done regardless of this param, ADDBA update always failed on those
> > HW.
>
> Seems like a legit problem, but
>
> > Fix this by only checking tid_ampdu_rx->timeout only when
> > SUPPORTS_REORDERING_BUFFER is not set.
>
> that doesn't seem right? Especially the way you implemented it, it won't
> even respond at all when it's an update and SUPPORTS_REORDERING_BUFFER
> is set.
I could be wrong but I think the patch format here make it difficult to
read. If it's an update and SUPPORTS_REORDERING_BUFFER is set, the
following "if" in the code (not fully visible in the diff here) will end
calling drv_ampdu_action().
>
> Seems we perhaps just need to store the timeout elsewhere?
>
That is another way of fixing that yes, but the question here is, don't
we want the driver to decide if it wants to support timeout update ?
> > @@ -374,14 +383,6 @@ void __ieee80211_start_rx_ba_session(struct sta_info *sta,
> > goto end;
> > }
> >
> > - ht_dbg_ratelimited(sta->sdata,
> > - "unexpected AddBA Req from %pM on tid %u\n",
> > - sta->sta.addr, tid);
> > -
> > - /* delete existing Rx BA session on the same tid */
> > - __ieee80211_stop_rx_ba_session(sta, tid, WLAN_BACK_RECIPIENT,
> > - WLAN_STATUS_UNSPECIFIED_QOS,
> > - false);
> > }
>
> Also, nit, but this leaves a blank line at the end of the block.
Sure will remove that if we finally decide to keep the fix as is.
Thanks for the review.
--
Remi
next prev parent reply other threads:[~2026-02-17 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 10:36 [PATCH wireless] wifi: mac80211: Fix ADDBA update when HW supports reordering Remi Pommarel
2026-02-17 11:30 ` Johannes Berg
2026-02-17 13:05 ` Remi Pommarel [this message]
2026-02-17 13:59 ` Johannes Berg
2026-02-17 14:38 ` Remi Pommarel
2026-02-17 16:00 ` Johannes Berg
2026-02-22 16:06 ` Remi Pommarel
2026-02-23 11:50 ` Johannes Berg
2026-02-23 13:25 ` Pablo MARTIN-GOMEZ
2026-02-26 15:49 ` Remi Pommarel
2026-02-26 16:28 ` Johannes Berg
2026-02-17 15:30 ` Pablo MARTIN-GOMEZ
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=aZRnlPA_uY9uWuKr@pilgrim \
--to=repk@triplefau.lt \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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.