From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dhyan K Prajapati <dhyan19022009@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Dhyan K Prajapati <dhyaan19022009@gmail.com>
Subject: Re: [PATCH] wifi: mac80211: skip BSS_CHANGED_TXPOWER notification for monitor mode
Date: Sat, 7 Feb 2026 10:41:18 +0100 [thread overview]
Message-ID: <66f082de-8f1e-464d-bedc-41c0a4db1f52@kernel.org> (raw)
In-Reply-To: <20260207050035.6720-1-dhyan19022009@gmail.com>
On 07/02/2026 06:00, Dhyan K Prajapati wrote:
> From: Dhyan K Prajapati <dhyaan19022009@gmail.com>
>
> Monitor mode interfaces don't maintain BSS context. The BSS_CHANGED_TXPOWER notification
> indicates transmit power constrains recieved from an associated access point which isn't really
> applicable to monitor mode as it does not associate with any BSS
>
> after a commit back in july 2025,("wifi: mac80211: fix WARN_ON for monitor mode
> on some devices") monitor interfaces with WANT_MONITOR_VIF began recieving link
> change notifications during ieee_add_virtual_monitor(), when ieee_link_use_channel()
> assigns a channel context it triggers ieee_recalc_power() which sends BSS_CHANGED_TXPOWER
> notifications to driver, driver using legacy bss_info_changed callbeack recieve
> link->conf as the bss_conf parameter for monitor mode that points to vif.bss_conf which is not fully initialised
> in monitor interfaces, so drivers like iwldvm dereference null and crash
> since BSS_CHANGED_TXPOWER notifications are meaningless for monitor mode, we can skip
> the notification entirely,monitor mode transmit power remains configurable via
You keep sending us microslop AI, so I don't think it is worth reviewing it.
> nl80211
> Hardware: Dell Latitude E6430
> Device: Intel Centrino Advanced-N 6205 [Taylor Peak]
>
> Crash trace:
> BUG: kernel NULL pointer dereference at 0000000000000000
> RIP: iwlagn_bss_info_changed+0x19d/0x640 [iwldvm]
> Call Trace:
> drv_link_info_changed+0x2b5/0x2c0
> ieee80211_link_info_change_notify+0x13d/0x160
> __ieee80211_recalc_txpower+0x44/0xd0
> ieee80211_recalc_txpower+0x5c/0x60
> ieee80211_assign_link_chanctx+0x182/0x410
> ieee80211_link_use_channel+0x413/0x450
> ieee80211_add_virtual_monitor+0x17c/0x2b0
>
> Tested-by: Dhyan K Prajapati <dhyan19022009@gmail.com>
No, wasn't. AI is not testing.
> Signed-off-by: Dhyan K Prajapati <dhyan19022009@gmail.com>
> ---
> net/mac80211/iface.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Best regards,
Krzysztof
prev parent reply other threads:[~2026-02-07 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 5:00 [PATCH] wifi: mac80211: skip BSS_CHANGED_TXPOWER notification for monitor mode Dhyan K Prajapati
2026-02-07 8:23 ` Lachlan Hodges
2026-02-07 9:41 ` Krzysztof Kozlowski [this message]
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=66f082de-8f1e-464d-bedc-41c0a4db1f52@kernel.org \
--to=krzk@kernel.org \
--cc=dhyaan19022009@gmail.com \
--cc=dhyan19022009@gmail.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