From: Julius Bairaktaris <julius@bairaktaris.de>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
John Crispin <john@phrozen.org>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
Rajkumar Manoharan <rmanohar@codeaurora.org>,
kbuild test robot <lkp@intel.com>
Subject: [PATCH ath-next v2 0/2] wifi: ath11k: do not fail down transitions of the station state
Date: Sat, 14 Nov 2026 23:56:41 +0100 [thread overview]
Message-ID: <20261114225643.962015-1-julius@bairaktaris.de> (raw)
mac80211 warns when a driver fails a down transition of the station
state, and ath11k does so while the firmware is down. Patch 2 fixes that.
Patch 1 is new: with the firmware down, a key whose removal failed stayed
in peer->keys[] although mac80211 had freed it.
I used Claude (Anthropic) to help write these patches.
Tested on an IPQ8074 AP (hw2.0 AHB, WLAN.HK.2.12-01460): the firmware was
crashed through debugfs and the station deleted at once. In 3 of 3 runs
with this series station del returned 0 with no mac80211 warning and no
key removal error, and the station re-associated. With the v1 patch alone,
one run logged "failed to remove peer key 0: -108" and "failed to clear all
peer keys for vdev 0: -108".
Changes in v2:
- New patch 1.
- Patch 2: continue the host cleanup after a failed early vdev stop and
a failed RTS/CTS update instead of returning from them (Sashiko review
of v1).
v1: https://lore.kernel.org/all/20261101174422.1275413-1-julius@bairaktaris.de/
Julius Bairaktaris (2):
wifi: ath11k: forget a key the firmware failed to remove
wifi: ath11k: do not fail down transitions of the station state
drivers/net/wireless/ath/ath11k/mac.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
base-commit: 1be6c8d3027d4a421dc46b93a89a196c61945614
--
2.53.0
next reply other threads:[~2026-11-14 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 22:56 Julius Bairaktaris [this message]
2026-11-14 22:56 ` [PATCH ath-next v2 1/2] wifi: ath11k: forget a key the firmware failed to remove Julius Bairaktaris
2026-11-14 22:56 ` [PATCH ath-next v2 2/2] wifi: ath11k: do not fail down transitions of the station state Julius Bairaktaris
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=20261114225643.962015-1-julius@bairaktaris.de \
--to=julius@bairaktaris.de \
--cc=ath11k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=quic_periyasa@quicinc.com \
--cc=quic_pradeepc@quicinc.com \
--cc=rameshkumar.sundaram@oss.qualcomm.com \
--cc=rmanohar@codeaurora.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
all inboxes | Powered by JetHome®