From: Joshua Klinesmith <joshuaklinesmith@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
Joshua Klinesmith <joshuaklinesmith@gmail.com>
Subject: [PATCH wireless v3 0/3] wifi: mt76: clear cipher state on key removal for WED offload
Date: Tue, 7 Apr 2026 01:39:14 -0400 [thread overview]
Message-ID: <20260407053917.75898-1-joshuaklinesmith@gmail.com> (raw)
Clear stale BSS cipher on group key removal so WED-offloaded
plaintext traffic is not dropped after switching from encrypted
to open/no-encryption mode.
Changes since v2:
- New patch 1/3: initialize hw_key_idx2 to -1 in mt76_wcid_init()
for consistent "no key" sentinel on both key index slots.
- Guard cipher clearing on both hw_key_idx == (u8)-1 AND
hw_key_idx2 == (u8)-1, so that GTK rotation (new key installed
before old removed) and BIGTK removal while another group key
is active do not trigger a premature zero-cipher BSS update.
Changes since v1:
- Rebased on current wireless tree.
Joshua Klinesmith (3):
wifi: mt76: initialize hw_key_idx2 in mt76_wcid_init
wifi: mt76: mt7915: clear cipher state on key removal for WED offload
wifi: mt76: mt7996: clear cipher state on key removal for WED offload
drivers/net/wireless/mediatek/mt76/mac80211.c | 1 +
.../net/wireless/mediatek/mt76/mt7915/main.c | 13 +++++++++++
.../net/wireless/mediatek/mt76/mt7996/main.c | 23 ++++++++++++++++---
3 files changed, 34 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-07 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 5:39 Joshua Klinesmith [this message]
2026-04-07 5:39 ` [PATCH wireless v3 1/3] wifi: mt76: initialize hw_key_idx2 in mt76_wcid_init Joshua Klinesmith
2026-04-07 5:39 ` [PATCH wireless v3 2/3] wifi: mt76: mt7915: clear cipher state on key removal for WED offload Joshua Klinesmith
2026-04-07 5:39 ` [PATCH wireless v3 3/3] wifi: mt76: mt7996: " Joshua Klinesmith
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=20260407053917.75898-1-joshuaklinesmith@gmail.com \
--to=joshuaklinesmith@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
/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