From: Johannes Berg <johannes@sipsolutions.net>
To: sanan.hasanou@gmail.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: Re: WARNING: at rate_control_rate_init, CPU: syz.NUM.NUM/NUM
Date: Fri, 26 Jun 2026 23:35:57 +0200 [thread overview]
Message-ID: <2bc48524a11ab0065b33c8a02b4c442665852d93.camel@sipsolutions.net> (raw)
In-Reply-To: <6a3eedeb.87857ece.10923b.5b31@mx.google.com> (sfid-20260626_232358_999373_6E38D4CE)
Dear people who run modified versions of syzkaller,
> Kernel Branch: 7.0-rc1
It might be a good idea not to use an old version.
> ------------[ cut here ]------------
> WARNING: at rate_control_rate_init+0x3a4/0x420 net/mac80211/rate.c:53, CPU#0: syz.7.23087/97240
and it might also be a good idea to check if syzbot already reported it:
https://syzkaller.appspot.com/bug?extid=9bdc0c5998ab45b05030
(FWIW, I'm not really entirely sure of the bisect)
Thanks for reducing (future) noise,
johannes
prev parent reply other threads:[~2026-06-26 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:23 WARNING: at rate_control_rate_init, CPU: syz.NUM.NUM/NUM sanan.hasanou
2026-06-26 21:35 ` Johannes Berg [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=2bc48524a11ab0065b33c8a02b4c442665852d93.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=contact@pgazz.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sanan.hasanou@gmail.com \
--cc=syzkaller@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