From: Johannes Berg <johannes@sipsolutions.net>
To: Slawomir Stepien <sst@poczta.fm>,
syzkaller-bugs@googlegroups.com, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, syzbot@lists.linux.dev,
syzbot+9bdc0c5998ab45b05030@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] mac80211: reject station addition if AP or MLO link is inactive
Date: Mon, 27 Jul 2026 10:19:05 +0200 [thread overview]
Message-ID: <9a9a794ad16663cfd7a652b83455ff16156b9baa.camel@sipsolutions.net> (raw)
In-Reply-To: <20260727074526.248393-1-sst@poczta.fm>
Hi,
On Mon, 2026-07-27 at 09:45 +0200, Slawomir Stepien wrote:
> Currently, userspace can issue a netlink command to add a station to
> an AP or P2P GO interface before the AP has fully started, or before
> a specific MLO link has begun beaconing. This will e.g. lead to a
> WARN_ON trigger:
>
> WARNING: net/mac80211/rate.c:51 at rate_control_rate_init+0x5a6/0x630
> ...
> Call Trace:
> <TASK>
> rate_control_rate_init_all_links+0xf4/0x190 net/mac80211/rate.c:84
> sta_apply_auth_flags+0x1bc/0x430 net/mac80211/cfg.c:2152
> sta_apply_parameters+0x126d/0x1b10 net/mac80211/cfg.c:2618
> ieee80211_add_station+0x3de/0x700 net/mac80211/cfg.c:2684
> rdev_add_station+0xfc/0x290 net/wireless/rdev-ops.h:201
> nl80211_new_station+0x1b4e/0x1fd0 net/wireless/nl80211.c:9505
>
> Fix this by introducing a two-tiered active state check in
> ieee80211_add_station():
Shouldn't we have enough information in cfg80211 to validate it there,
benefiting other drivers?
johannes
next prev parent reply other threads:[~2026-07-27 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 7:45 Slawomir Stepien
2026-07-27 8:19 ` Johannes Berg [this message]
2026-07-27 9:22 ` Slawomir Stepien
2026-07-27 9:25 ` Johannes Berg
2026-07-27 10:26 ` Slawomir Stepien
2026-07-27 13:26 ` Slawomir Stepien
2026-07-31 12:40 ` Johannes Berg
2026-08-03 13:09 ` Slawomir Stepien
2026-08-03 13:15 ` Johannes Berg
2026-07-27 13:44 ` [syzbot ci] " syzbot ci
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=9a9a794ad16663cfd7a652b83455ff16156b9baa.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sst@poczta.fm \
--cc=syzbot+9bdc0c5998ab45b05030@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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®