From: Alex Gavin <a_gavin@icloud.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>, Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Matvey Kovalev <matvey.kovalev@ispras.ru>,
lvc-project@linuxtesting.org
Subject: Re: [PATCH mt76 1/2] Revert "wifi: mt76: mt792x: improve monitor interface handling"
Date: Thu, 20 Nov 2025 21:42:18 -0800 [thread overview]
Message-ID: <780b6778-ea0e-4fc9-8f35-83b5cd4940af@icloud.com> (raw)
In-Reply-To: <20251027111843.38975-1-pchelkin@ispras.ru>
On 10/27/25 04:18, Fedor Pchelkin wrote:
> This reverts commit 55e95ce469d0c61041bae48b2ebb7fcbf6d1ba7f.
>
> mt792x drivers don't seem to support multi-radio devices yet. At least
> they don't mess with `struct wiphy_radio` at the moment.
>
> Packet capturing on monitor interface doesn't work after the blamed patch:
>
> tcpdump -i wls6mon -n -vvv
>
> Revert the NO_VIRTUAL_MONITOR feature for now to resolve the issue.
>
> Found by Linux Verification Center (linuxtesting.org).
>
> Fixes: 55e95ce469d0 ("wifi: mt76: mt792x: improve monitor interface handling")
> Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
> ---
>
> Can't answer exactly *why* the capturing doesn't work after the patch:
> probably because the driver is just not prepared for NO_VIRTUAL_MONITOR.
> The feature isn't too obvious, especially that for some reason it was set
> in mt792x alongside WANT_MONITOR_VIF. With a quick glance I might
> conclude that NO_VIRTUAL_MONITOR overrides WANT_MONITOR_VIF, they don't
> look compatible.
>
> drivers/net/wireless/mediatek/mt76/mt792x_core.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/wireless/mediatek/mt76/mt792x_core.c b/drivers/net/wireless/mediatek/mt76/mt792x_core.c
> index 5b50bf94996e..f2ed16feb6c1 100644
> --- a/drivers/net/wireless/mediatek/mt76/mt792x_core.c
> +++ b/drivers/net/wireless/mediatek/mt76/mt792x_core.c
> @@ -688,7 +688,6 @@ int mt792x_init_wiphy(struct ieee80211_hw *hw)
> ieee80211_hw_set(hw, SUPPORTS_DYNAMIC_PS);
> ieee80211_hw_set(hw, SUPPORTS_VHT_EXT_NSS_BW);
> ieee80211_hw_set(hw, CONNECTION_MONITOR);
> - ieee80211_hw_set(hw, NO_VIRTUAL_MONITOR);
> ieee80211_hw_set(hw, SUPPORTS_MULTI_BSSID);
> ieee80211_hw_set(hw, SUPPORTS_ONLY_HE_MULTI_BSSID);
>
This patch fixed monitor vif-only packet capture for me when using both mt7921 and mt7921au chipset
radios. Without it I was only seeing broadcast and multicast traffic I believe. Tested using vanilla
6.18.0-rc6 as base.
prev parent reply other threads:[~2025-11-21 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 11:18 Fedor Pchelkin
2025-10-27 11:18 ` [PATCH mt76 2/2] wifi: mt76: adjust BSS conf pointer handling Fedor Pchelkin
2025-11-21 5:42 ` Alex Gavin [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=780b6778-ea0e-4fc9-8f35-83b5cd4940af@icloud.com \
--to=a_gavin@icloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=matvey.kovalev@ispras.ru \
--cc=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=pchelkin@ispras.ru \
--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
all inboxes | Powered by JetHome®