From: syzbot <syzbot+50f7e8d06c3768dd97f3@syzkaller.appspotmail.com>
To: andrei.otcheretianski@intel.com, asmadeus@codewreck.org,
davem@davemloft.net, edumazet@google.com, ericvh@gmail.com,
fgheet255t@gmail.com, johannes.berg@intel.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com,
v9fs-developer@lists.sourceforge.net
Subject: Re: [syzbot] possible deadlock in p9_req_put
Date: Mon, 08 Aug 2022 22:05:15 -0700 [thread overview]
Message-ID: <000000000000bc500505e5c7e01f@google.com> (raw)
In-Reply-To: <000000000000cad57405e5b5dbb7@google.com>
syzbot has bisected this issue to:
commit 54283409cd162fc60480df514924ed4cb313735e
Author: Andrei Otcheretianski <andrei.otcheretianski@intel.com>
Date: Tue Jun 14 14:20:04 2022 +0000
wifi: mac80211: Consider MLO links in offchannel logic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1046e22a080000
start commit: ca688bff68bc Add linux-next specific files for 20220808
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1246e22a080000
console output: https://syzkaller.appspot.com/x/log.txt?x=1446e22a080000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c20e006003cdecb
dashboard link: https://syzkaller.appspot.com/bug?extid=50f7e8d06c3768dd97f3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f6ea66080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1640de8e080000
Reported-by: syzbot+50f7e8d06c3768dd97f3@syzkaller.appspotmail.com
Fixes: 54283409cd16 ("wifi: mac80211: Consider MLO links in offchannel logic")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-08-09 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 7:35 [syzbot] possible deadlock in p9_req_put syzbot
2022-08-08 14:14 ` syzbot
2022-08-09 5:05 ` 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=000000000000bc500505e5c7e01f@google.com \
--to=syzbot+50f7e8d06c3768dd97f3@syzkaller.appspotmail.com \
--cc=andrei.otcheretianski@intel.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@gmail.com \
--cc=fgheet255t@gmail.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=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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).