From: syzbot <syzbot+dd4779978217b1973180@syzkaller.appspotmail.com>
To: SHA-cyfmac-dev-list@infineon.com, ajay.kathat@microchip.com,
amitkarwar@gmail.com, aspriel@gmail.com,
brcm80211-dev-list.pdl@broadcom.com,
claudiu.beznea@microchip.com, davem@davemloft.net,
edumazet@google.com, franky.lin@broadcom.com,
ganapathi017@gmail.com, geomatsi@gmail.com,
gregkh@linuxfoundation.org, hante.meuleman@broadcom.com,
huxinming820@gmail.com, imitsyanko@quantenna.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, kvalo@kernel.org,
libertas-dev@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
sharvari.harisangam@nxp.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [wireless?] WARNING in ieee80211_bss_info_change_notify (2)
Date: Fri, 13 Oct 2023 16:50:31 -0700 [thread overview]
Message-ID: <000000000000c19b400607a1b88c@google.com> (raw)
In-Reply-To: <0000000000006a3d0d060785f027@google.com>
syzbot has bisected this issue to:
commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1
Author: Johannes Berg <johannes.berg@intel.com>
Date: Thu Apr 14 14:50:57 2022 +0000
wifi: cfg80211: do some rework towards MLO link APIs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13fdd89d680000
start commit: ce583d5fb9d3 Merge tag 'for-v6.6-rc2' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1003d89d680000
console output: https://syzkaller.appspot.com/x/log.txt?x=17fdd89d680000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d83dadac33c08b7
dashboard link: https://syzkaller.appspot.com/bug?extid=dd4779978217b1973180
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157a58e5680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=170cf875680000
Reported-by: syzbot+dd4779978217b1973180@syzkaller.appspotmail.com
Fixes: 7b0a0e3c3a88 ("wifi: cfg80211: do some rework towards MLO link APIs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-13 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:41 [syzbot] [net?] [wireless?] WARNING in ieee80211_bss_info_change_notify (2) syzbot
2023-10-13 13:48 ` syzbot
2023-10-13 23:50 ` syzbot [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=000000000000c19b400607a1b88c@google.com \
--to=syzbot+dd4779978217b1973180@syzkaller.appspotmail.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=ajay.kathat@microchip.com \
--cc=amitkarwar@gmail.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=ganapathi017@gmail.com \
--cc=geomatsi@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hante.meuleman@broadcom.com \
--cc=huxinming820@gmail.com \
--cc=imitsyanko@quantenna.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharvari.harisangam@nxp.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;
as well as URLs for NNTP newsgroup(s).