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 1/2] wifi: ath11k: forget a key the firmware failed to remove
Date: Sat, 14 Nov 2026 23:56:42 +0100 [thread overview]
Message-ID: <20261114225643.962015-2-julius@bairaktaris.de> (raw)
In-Reply-To: <20261114225643.962015-1-julius@bairaktaris.de>
mac80211 frees a key after set_key() with DISABLE_KEY whatever the
driver returns. When the WMI command to remove the key fails, ath11k
returns before it clears peer->keys[], so the peer keeps a pointer to
the freed key. While the firmware is down, removing a station frees its
keys this way, and the following ASSOC -> AUTH transition passes the
freed keys to ath11k_install_key() from ath11k_clear_peer_keys().
Clear the host reference to a disabled key also when the firmware
command fails.
Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.12-01460
Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
---
Changes in v2: new patch.
drivers/net/wireless/ath/ath11k/mac.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath11k/mac.c b/drivers/net/wireless/ath/ath11k/mac.c
index 1a237adaa37d..9c3f577c9562 100644
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -4615,17 +4615,22 @@ static int ath11k_mac_op_set_key(struct ieee80211_hw *hw, enum set_key_cmd cmd,
is_ap_with_no_sta = (vif->type == NL80211_IFTYPE_AP &&
!arvif->num_stations);
if (flags == WMI_KEY_PAIRWISE || cmd == SET_KEY || is_ap_with_no_sta) {
+ /* mac80211 frees a disabled key whatever this returns, so
+ * forget it below even if the firmware did not remove it.
+ */
ret = ath11k_install_key(arvif, key, cmd, peer_addr, flags);
if (ret) {
ath11k_warn(ab, "ath11k_install_key failed (%d)\n", ret);
- goto exit;
+ if (cmd == SET_KEY)
+ goto exit;
}
ret = ath11k_dp_peer_rx_pn_replay_config(arvif, peer_addr, cmd, key);
if (ret) {
ath11k_warn(ab, "failed to offload PN replay detection %d\n",
ret);
- goto exit;
+ if (cmd == SET_KEY)
+ goto exit;
}
if (flags == WMI_KEY_GROUP && cmd == SET_KEY && is_ap_with_no_sta)
--
2.53.0
next prev parent 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 [PATCH ath-next v2 0/2] wifi: ath11k: do not fail down transitions of the station state Julius Bairaktaris
2026-11-14 22:56 ` Julius Bairaktaris [this message]
2026-11-14 22:56 ` [PATCH ath-next v2 2/2] " 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-2-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®