From: syzbot <syzbot+0d8542c90a512dc95185@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
ming.lei@redhat.com, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [trace?] possible deadlock in blk_trace_setup
Date: Mon, 20 Jan 2025 16:22:02 -0800 [thread overview]
Message-ID: <678ee8aa.050a0220.15cac.0002.GAE@google.com> (raw)
In-Reply-To: <672751ef.050a0220.35b515.0199.GAE@google.com>
syzbot has bisected this issue to:
commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri Oct 25 00:37:20 2024 +0000
block: model freeze & enter queue as lock for supporting lockdep
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1536b9df980000
start commit: 5b913f5d7d7f Add linux-next specific files for 20241106
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1736b9df980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1336b9df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=27aeebbe9ce2cea
dashboard link: https://syzkaller.appspot.com/bug?extid=0d8542c90a512dc95185
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=167b3d5f980000
Reported-by: syzbot+0d8542c90a512dc95185@syzkaller.appspotmail.com
Fixes: f1be1788a32e ("block: model freeze & enter queue as lock for supporting lockdep")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-01-21 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 10:35 [syzbot] [block?] [trace?] possible deadlock in blk_trace_setup syzbot
2025-01-21 0:22 ` 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=678ee8aa.050a0220.15cac.0002.GAE@google.com \
--to=syzbot+0d8542c90a512dc95185@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ming.lei@redhat.com \
--cc=rostedt@goodmis.org \
--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).