From: syzbot <syzbot+62d7eef57b09bfebcd84@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com
Subject: Re: [syzbot] [wireless?] WARNING in rate_control_rate_init (2)
Date: Tue, 28 Nov 2023 15:57:04 -0800 [thread overview]
Message-ID: <000000000000efd864060b3f2cf0@google.com> (raw)
In-Reply-To: <000000000000efc64705ff8286a1@google.com>
syzbot has bisected this issue to:
commit b303835dabe0340f932ebb4e260d2229f79b0684
Author: Johannes Berg <johannes.berg@intel.com>
Date: Sat Jul 23 20:08:49 2022 +0000
wifi: mac80211: accept STA changes without link changes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=125a86dce80000
start commit: a214724554ae Merge tag 'wireless-next-2023-11-27' of git:/..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=115a86dce80000
console output: https://syzkaller.appspot.com/x/log.txt?x=165a86dce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=abf6d5a82dab01fe
dashboard link: https://syzkaller.appspot.com/bug?extid=62d7eef57b09bfebcd84
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a4fc64e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1363b22ce80000
Reported-by: syzbot+62d7eef57b09bfebcd84@syzkaller.appspotmail.com
Fixes: b303835dabe0 ("wifi: mac80211: accept STA changes without link changes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-28 23:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 15:15 [syzbot] [wireless?] WARNING in rate_control_rate_init (2) syzbot
2023-11-28 23:57 ` syzbot [this message]
2023-11-29 3:06 ` [syzbot] [wireless?] WARNING in rate_control_rate_init syzbot
2023-11-29 4:04 ` syzbot
2023-11-29 5:48 ` [PATCH] wifi: mac80211: sband's null check should precede params Edward Adam Davis
2023-11-29 6:57 ` Johannes Berg
2023-11-29 8:18 ` Edward Adam Davis
2023-11-29 8:33 ` Johannes Berg
2023-11-29 8:48 ` Edward Adam Davis
2023-11-29 9:15 ` Johannes Berg
2023-11-29 12:17 ` [PATCH V2] wifi: mac80211: check if the existing link config remains unchanged Edward Adam Davis
2023-11-29 11:04 ` [syzbot] [wireless?] WARNING in rate_control_rate_init syzbot
2023-11-29 11:26 ` syzbot
[not found] <tencent_99AEEDA6CECC79B26F902CE56F74966CE90A@qq.com>
2023-11-29 3:43 ` [syzbot] [wireless?] WARNING in rate_control_rate_init (2) syzbot
[not found] <tencent_A6904B6E757F76B566FE3D0F37BE966C3609@qq.com>
2023-11-29 4:40 ` syzbot
[not found] <tencent_22044BD21BDE25BEBA3ABB5233139EBD1B08@qq.com>
2023-11-29 11:19 ` syzbot
[not found] <tencent_851BBE2546BAA8BB4C33AA9E661BD54B2808@qq.com>
2023-11-29 12:02 ` syzbot
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=000000000000efd864060b3f2cf0@google.com \
--to=syzbot+62d7eef57b09bfebcd84@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.