From: syzbot <syzbot+9b145229d11aa73e4571@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hdanton@sina.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
syzkaller-bugs@googlegroups.com,
thomas.hellstrom@linux.intel.com
Subject: Re: [syzbot] [block?] possible deadlock in loop_set_status
Date: Fri, 02 May 2025 04:51:02 -0700 [thread overview]
Message-ID: <6814b1a6.050a0220.33cf57.0000.GAE@google.com> (raw)
In-Reply-To: <6741e9d0.050a0220.1cc393.0014.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=1411b774580000
start commit: f1a3944c860b Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1611b774580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1211b774580000
kernel config: https://syzkaller.appspot.com/x/.config?x=90837c100b88a636
dashboard link: https://syzkaller.appspot.com/bug?extid=9b145229d11aa73e4571
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163650d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11652270580000
Reported-by: syzbot+9b145229d11aa73e4571@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
next prev parent reply other threads:[~2025-05-02 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 14:42 [syzbot] [block?] possible deadlock in loop_set_status syzbot
2024-11-28 12:37 ` Ming Lei
2025-03-01 10:18 ` syzbot
2025-03-01 13:47 ` Hillf Danton
2025-03-01 14:15 ` syzbot
2025-05-02 11:51 ` syzbot [this message]
2025-07-05 15:51 ` Tetsuo Handa
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=6814b1a6.050a0220.33cf57.0000.GAE@google.com \
--to=syzbot+9b145229d11aa73e4571@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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