mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+468656785707b0e995df@syzkaller.appspotmail.com>,
	 linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	 netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING: net/mac80211/tx.c:LINE at __ieee80211_beacon_get, CPU: syz.NUM.NUM/NUM
Date: Tue, 17 Jun 2025 11:50:32 +0200	[thread overview]
Message-ID: <49456d11ed8d4ff3adc71286b17dc657a6db131b.camel@sipsolutions.net> (raw)
In-Reply-To: <CANp29Y5+W426u0jUz0PT=zVde+QqSD9H1fLpTuaKSzCLrt5FcA@mail.gmail.com> (sfid-20250617_114851_219552_D4A7444C)

On Tue, 2025-06-17 at 11:48 +0200, Aleksandr Nogikh wrote:
> On Tue, Jun 17, 2025 at 11:43 AM Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > 
> > On Tue, 2025-06-17 at 11:34 +0200, Aleksandr Nogikh wrote:
> > > #syz dup: WARNING in __ieee80211_beacon_get
> > > 
> > 
> > Not just this one :)
> > 
> > https://lore.kernel.org/linux-wireless/20250617104902.146e10919be1.I85f352ca4a2dce6f556e5ff45ceaa5f3769cb5ce@changeid/
> > 
> 
> Ah, interesting :)
> 
> FWIW, in this particular case, syzbot sent the duplicate report
> because the WARNING format has somewhat changed in the latest
> linux-next. So before we updated syzbot's parsing rules, it had
> managed to re-report quite a few duplicates.

Right, I had noticed that, but then I looked and the old counter is
already at well over 100k so I decided to finally look at it again ;-)

This is a really long-standing problem that we discussed a few times in
the past I think, and basically the system is loaded enough that the
hwsim hrtimer can fire on time and pull the beacon, but the workqueues
are overloaded and cannot do the necessary work within the ~100ms beacon
interval ...

Should be rare in practice, but a WARN_ON() that doesn't say anything
about what's going on doesn't help anyway.

johannes

  reply	other threads:[~2025-06-17  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  2:32 syzbot
2025-06-17  9:34 ` Aleksandr Nogikh
2025-06-17  9:43   ` Johannes Berg
2025-06-17  9:48     ` Aleksandr Nogikh
2025-06-17  9:50       ` Johannes Berg [this message]
2025-06-17  9:59         ` Aleksandr Nogikh

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=49456d11ed8d4ff3adc71286b17dc657a6db131b.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=syzbot+468656785707b0e995df@syzkaller.appspotmail.com \
    --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®