From: syzbot <syzbot+51a42f7c2e399392ea82@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@qq.com, kuba@kernel.org,
kvalo@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
srini.raju@purelifi.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in plfxlc_mac_release
Date: Thu, 28 Nov 2024 03:58:01 -0800 [thread overview]
Message-ID: <67485ac9.050a0220.253251.0082.GAE@google.com> (raw)
In-Reply-To: <000000000000ac553b061e675573@google.com>
syzbot has bisected this issue to:
commit 68d57a07bfe5bb29b80cd8b8fa24c9d1ea104124
Author: Srinivasan Raju <srini.raju@purelifi.com>
Date: Thu Feb 24 18:20:07 2022 +0000
wireless: add plfxlc driver for pureLiFi X, XL, XC devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15001f5f980000
start commit: cfba9f07a1d6 Add linux-next specific files for 20241122
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17001f5f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13001f5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=45719eec4c74e6ba
dashboard link: https://syzkaller.appspot.com/bug?extid=51a42f7c2e399392ea82
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101a59c0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bcc778580000
Reported-by: syzbot+51a42f7c2e399392ea82@syzkaller.appspotmail.com
Fixes: 68d57a07bfe5 ("wireless: add plfxlc driver for pureLiFi X, XL, XC devices")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-28 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 18:50 [syzbot] [wireless?] WARNING in plfxlc_mac_release syzbot
2024-07-30 4:28 ` [PATCH] wifi: plfxlc: remove assert for mac->lock Edward Adam Davis
2024-07-30 10:35 ` Kalle Valo
2024-07-30 11:46 ` Edward Adam Davis
2024-11-28 11:58 ` 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=67485ac9.050a0220.253251.0082.GAE@google.com \
--to=syzbot+51a42f7c2e399392ea82@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srini.raju@purelifi.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).