From: Enver Ikromov <owner@ph4ntom-rev.uz>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Zong-Zhe Yang <kevin_yang@realtek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Enver Ikromov <owner@ph4ntom-rev.uz>
Subject: [PATCH rtw-next v6 0/5] wifi: rtw89: monitor mode and raw frame injection fixes
Date: Tue, 17 Nov 2026 14:41:30 +0500 [thread overview]
Message-ID: <20261117094135.1772-1-owner@ph4ntom-rev.uz> (raw)
This series fixes a NULL vif dereference and a negative radiotap rate
index bug on the TX path, restores the operating channel after monitor
down/up on non-chanctx devices, and fixes control-frame seq_ctrl reads,
sequence preservation, NO_ACK, and retry limits for raw 802.11 frame
injection.
Tested on RTL8852AE (10ec:8852, firmware 0.13.36.2) across 2.4 GHz and
5 GHz.
Changes in v6:
- Focus the series strictly on the standalone monitor interface case
(plus the concurrent NULL-vif crash guard in patch 1), dropping former
patches 3, 4, 5, 6, and 8 (RX filter changes, RCU pure_monitor_mode_vif,
AP self role, NL80211_FEATURE_ACTIVE_MONITOR, and host TX hook skips).
- Rewrite all commit messages concisely without function-level flow.
- Patch 1: use vif_to_rtwvif_safe().
- Patch 2: clamp negative rate indices to 0 with max_t().
- Patch 3 (was 10): move before injection changes, add
rtwdev->support_chanctx, and reuse IEEE80211_CONF_CHANGE_CHANNEL in
rtw89_ops_config().
- Patch 4 (was 7): keep control frames on the AC queue and only set
seq = 0 for control frames.
- Patch 5 (was 9): simplify ASSIGN_SEQ handling and drop dead RTS/CTS,
rate-index clamping, upd_wlan_hdr, and pci.c counter changes.
- Rebase onto latest rtw-next and wrap all lines to <= 80 columns.
Changes in v5:
- Split the NULL vif fix and negative rate index fix out as standalone
patches 1-2 with Fixes: and Cc: stable tags.
- Split monitor injection into focused patches.
- Honor ASSIGN_SEQ, retries, and NO_ACK for injected frames.
- Restore channel on leaving idle for non-chanctx devices.
Changes in v3:
- Split into a patch series and use driver abstractions instead of
direct register writes.
v5: https://lore.kernel.org/linux-wireless/20261113235211.1911-1-owner@ph4ntom-rev.uz/
v3: https://lore.kernel.org/linux-wireless/20261104203051.564-1-owner@ph4ntom-rev.uz/
v2: https://lore.kernel.org/linux-wireless/179371849554.20972.16232816164394690660@ph4ntom-rev.uz/
v1 (RFC): https://lore.kernel.org/linux-wireless/1a196d6dfbc.35537d221913104450.3720060455831933789@zoho.com/
Enver Ikromov (5):
wifi: rtw89: avoid NULL vif dereference in rtw89_ops_tx()
wifi: rtw89: handle negative rate index for injected frames
wifi: rtw89: restore channel when leaving idle on non-chanctx devices
wifi: rtw89: avoid reading seq_ctrl on control frames
wifi: rtw89: honor ASSIGN_SEQ, retries, and NO_ACK for injected frames
drivers/net/wireless/realtek/rtw89/core.c | 27 ++++++++++++++++---
drivers/net/wireless/realtek/rtw89/core.h | 3 +++
drivers/net/wireless/realtek/rtw89/mac.h | 2 ++
drivers/net/wireless/realtek/rtw89/mac80211.c | 16 ++++++++++-
4 files changed, 44 insertions(+), 4 deletions(-)
base-commit: badf4c3c7679871a50cff1150f66e63187201757
--
2.56.0.windows.4
next reply other threads:[~2026-11-17 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:41 Enver Ikromov [this message]
2026-11-17 9:41 ` [PATCH rtw-next v6 1/5] wifi: rtw89: avoid NULL vif dereference in rtw89_ops_tx() Enver Ikromov
2026-11-17 9:41 ` [PATCH rtw-next v6 2/5] wifi: rtw89: handle negative rate index for injected frames Enver Ikromov
2026-11-17 9:41 ` [PATCH rtw-next v6 3/5] wifi: rtw89: restore channel when leaving idle on non-chanctx devices Enver Ikromov
2026-11-18 6:30 ` Zong-Zhe Yang
2026-11-17 9:41 ` [PATCH rtw-next v6 4/5] wifi: rtw89: avoid reading seq_ctrl on control frames Enver Ikromov
2026-11-17 9:41 ` [PATCH rtw-next v6 5/5] wifi: rtw89: honor ASSIGN_SEQ, retries, and NO_ACK for injected frames Enver Ikromov
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=20261117094135.1772-1-owner@ph4ntom-rev.uz \
--to=owner@ph4ntom-rev.uz \
--cc=kevin_yang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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
all inboxes | Powered by JetHome®