From: syzbot <syzbot+3dbc6142c85cc77eaf04@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bvanassche@acm.org, hdanton@sina.com,
josef@toxicpanda.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
nbd@other.debian.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com,
thomas.hellstrom@linux.intel.com
Subject: Re: [syzbot] [nbd?] possible deadlock in nbd_queue_rq
Date: Tue, 16 Sep 2025 11:18:03 -0700 [thread overview]
Message-ID: <68c9a9db.050a0220.2ff435.040b.GAE@google.com> (raw)
In-Reply-To: <686aa557.a00a0220.c7b3.005d.GAE@google.com>
syzbot has bisected this issue to:
commit ffa1e7ada456087c2402b37cd6b2863ced29aff0
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Date: Tue Mar 18 09:55:48 2025 +0000
block: Make request_queue lockdep splats show up earlier
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11eef762580000
start commit: f83ec76bf285 Linux 6.17-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13eef762580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15eef762580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f01d8629880e620
dashboard link: https://syzkaller.appspot.com/bug?extid=3dbc6142c85cc77eaf04
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1009bb62580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14833b12580000
Reported-by: syzbot+3dbc6142c85cc77eaf04@syzkaller.appspotmail.com
Fixes: ffa1e7ada456 ("block: Make request_queue lockdep splats show up earlier")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-16 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 16:33 [syzbot] [nbd?] possible deadlock in nbd_queue_rq syzbot
2025-07-07 0:59 ` Hillf Danton
2025-07-07 17:39 ` Bart Van Assche
2025-07-08 0:18 ` Hillf Danton
2025-07-08 0:52 ` Tetsuo Handa
2025-07-08 1:24 ` Hillf Danton
2025-07-08 2:19 ` Tetsuo Handa
2025-07-08 16:23 ` Bart Van Assche
2025-09-15 2:16 ` syzbot
2025-09-16 18:18 ` 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=68c9a9db.050a0220.2ff435.040b.GAE@google.com \
--to=syzbot+3dbc6142c85cc77eaf04@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hdanton@sina.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nbd@other.debian.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=thomas.hellstrom@linux.intel.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).