From: Johannes Berg <johannes@sipsolutions.net>
To: Suraj P Kizhakkethil <suraj.kizhakkethil@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next 1/2] wifi: mac80211: set band information for NULL packets only for non-MLO stations
Date: Thu, 08 Jan 2026 13:19:42 +0100 [thread overview]
Message-ID: <67b8cc599e923433eec6c8baff72583c47a53cfd.camel@sipsolutions.net> (raw)
In-Reply-To: <20251127140555.472327-2-suraj.kizhakkethil@oss.qualcomm.com>
On Thu, 2025-11-27 at 19:35 +0530, Suraj P Kizhakkethil wrote:
> Currently, when sending a NULL packet to probe a station, the band
> information is derived from the chanctx_conf in the mac80211 vif's
> bss_conf. However, for MLO, chanctx_conf is not assigned to the vif's
> bss_conf; instead it is assigned on a per-link basis. As a result,
> for MLO, sending a NULL packet to probe will trigger a warning.
>
> WARNING: net/mac80211/cfg.c:4593 at ieee80211_probe_client+0x1a8/0x1e0 [mac80211], CPU#2: hostapd/241
> Call trace:
> ieee80211_probe_client+0x1a8/0x1e0 [mac80211] (P)
> nl80211_probe_client+0xac/0x170 [cfg80211]
> genl_family_rcv_msg_doit+0xc8/0x134
> genl_rcv_msg+0x200/0x280
> netlink_rcv_skb+0x38/0xfc
> genl_rcv+0x34/0x48
> netlink_unicast+0x228/0x334
> netlink_sendmsg+0x158/0x364
> ____sys_sendmsg+0x1f4/0x21c
> ___sys_sendmsg+0x98/0xc0
> __sys_sendmsg+0x74/0xd0
> __arm64_sys_sendmsg+0x20/0x28
> invoke_syscall.constprop.0+0x4c/0xd0
> do_el0_svc+0x3c/0xd0
> el0_svc+0x28/0xb8
> el0t_64_sync_handler+0x98/0xdc
> el0t_64_sync+0x154/0x158
> ---[ end trace 0000000000000000 ]---
>
> For NULL packets sent to probe stations, set the band information only
> for non-MLD case, since MLD transmissions does not rely on band. For
> MLD connections, set the link ID as unspecified to allow the driver
> to select the appropriate link. The case specific to non-MLO stations
> connected to an MLD AP will be addressed in a follow up patch.
Technically "AP MLD" ;)
But I was more wondering about the use of "MLD connections", which seems
odd to me (vs. "MLO connections")? Connections between MLDs? MLD is an
entity, MLO is the mode of operation?
> + if (ieee80211_vif_is_mld(&sdata->vif))
> + info->control.flags |= IEEE80211_TX_CTRL_MLO_LINK_UNSPEC;
I don't see why it should be set conditionally, it should be ignored
anyway by non-MLO drivers? Or maybe if you'd want it zero for t hose
then do that explicitly?
I'm really commenting here because it gets messy in the next patch, see
also there.
johannes
next prev parent reply other threads:[~2026-01-08 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 14:05 [PATCH wireless-next 0/2] wifi: mac80211: Fix issues related to sending NULL packets to probe stations Suraj P Kizhakkethil
2025-11-27 14:05 ` [PATCH wireless-next 1/2] wifi: mac80211: set band information for NULL packets only for non-MLO stations Suraj P Kizhakkethil
2026-01-08 12:19 ` Johannes Berg [this message]
2026-02-14 7:36 ` Suraj P Kizhakkethil
2025-11-27 14:05 ` [PATCH wireless-next 2/2] wifi: mac80211: set addr2/addr3 to link address for NULL packets to " Suraj P Kizhakkethil
2026-01-08 12:20 ` Johannes Berg
2026-02-14 7:37 ` Suraj P Kizhakkethil
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=67b8cc599e923433eec6c8baff72583c47a53cfd.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=suraj.kizhakkethil@oss.qualcomm.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