From: syzbot <syzbot+d073f255508305ccb3fd@syzkaller.appspotmail.com>
To: angelogioacchino.delregno@collabora.com, davem@davemloft.net,
edumazet@google.com, johannes.berg@intel.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, matthias.bgg@gmail.com,
michael-cy.lee@mediatek.com, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in cfg80211_bss_color_notify
Date: Sun, 18 Aug 2024 12:19:02 -0700 [thread overview]
Message-ID: <000000000000ad7bab061ffa109d@google.com> (raw)
In-Reply-To: <000000000000612f290618eee3e5@google.com>
syzbot suspects this issue was fixed by commit:
commit 4044b23781104801f70c4a4ec3ca090730a161c5
Author: Michael-CY Lee <michael-cy.lee@mediatek.com>
Date: Fri Jul 5 07:43:46 2024 +0000
wifi: mac80211: do not check BSS color collision in certain cases
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=130f62dd980000
start commit: f6f25eebe05f Merge branch 'wangxun-fixes'
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=bddb81daac38d475
dashboard link: https://syzkaller.appspot.com/bug?extid=d073f255508305ccb3fd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f9ec92980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1595fa84980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: mac80211: do not check BSS color collision in certain cases
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2024-08-18 19:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000612f290618eee3e5@google.com>]
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=000000000000ad7bab061ffa109d@google.com \
--to=syzbot+d073f255508305ccb3fd@syzkaller.appspotmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=michael-cy.lee@mediatek.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).