Linux wireless drivers development
 help / color / mirror / Atom feed
From: David Carlier <devnexen@gmail.com>
To: Jeff Chen <jeff.chen_1@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Carlier <devnexen@gmail.com>
Subject: [PATCH wireless-next 0/2] wifi: nxpwifi: fix two block ack teardown bugs
Date: Wed, 26 Aug 2026 00:17:08 +0100	[thread overview]
Message-ID: <20260825231834.244783-1-devnexen@gmail.com> (raw)

Two independent bugs in the block ack teardown paths, both found by code
inspection on next-20260825 and compile tested only.

The first leaves nxpwifi_11n_delete_tx_ba_stream_tbl_entry() unable to
delete anything, so Tx BA stream entries leak on every teardown and
aggregation eventually stops being negotiated. The second holds the RCU
read lock across a teardown that sleeps, which splats under
CONFIG_DEBUG_ATOMIC_SLEEP when a station deauthenticates from the AP.

David Carlier (2):
  wifi: nxpwifi: fix inverted check in Tx BA stream entry deletion
  wifi: nxpwifi: do not delete Rx reorder entries under RCU

 drivers/net/wireless/nxp/nxpwifi/11n.c           |  2 +-
 drivers/net/wireless/nxp/nxpwifi/11n_rxreorder.c | 11 ++++++-----
 2 files changed, 7 insertions(+), 6 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-08-25 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 23:17 David Carlier [this message]
2026-08-25 23:17 ` [PATCH wireless-next 1/2] wifi: nxpwifi: fix inverted check in Tx BA stream entry deletion David Carlier
2026-08-25 23:17 ` [PATCH wireless-next 2/2] wifi: nxpwifi: do not delete Rx reorder entries under RCU David Carlier

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=20260825231834.244783-1-devnexen@gmail.com \
    --to=devnexen@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=jeff.chen_1@nxp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox