From: syzbot <syzbot+153e64c0aa875d7e4c37@syzkaller.appspotmail.com>
To: axboe@kernel.dk, dlemoal@kernel.org, johannes.thumshirn@wdc.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, martin.petersen@oracle.com,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [trace?] WARNING in __blk_add_trace
Date: Sat, 25 Oct 2025 05:19:02 -0700 [thread overview]
Message-ID: <68fcc036.a00a0220.9662e.0017.GAE@google.com> (raw)
In-Reply-To: <68fc07a0.a70a0220.3bf6c6.01aa.GAE@google.com>
syzbot has bisected this issue to:
commit f9ee38bbf70fb20584625849a253c8652176fa66
Author: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Date: Wed Oct 22 11:41:12 2025 +0000
blktrace: add block trace commands for zone operations
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1750c7e2580000
start commit: 72fb0170ef1f Add linux-next specific files for 20251024
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14d0c7e2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10d0c7e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f02d98016cc9c137
dashboard link: https://syzkaller.appspot.com/bug?extid=153e64c0aa875d7e4c37
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145ae3cd980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f58be2580000
Reported-by: syzbot+153e64c0aa875d7e4c37@syzkaller.appspotmail.com
Fixes: f9ee38bbf70f ("blktrace: add block trace commands for zone operations")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-25 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 23:11 [syzbot] [block?] [trace?] WARNING in __blk_add_trace syzbot
2025-10-25 12:19 ` syzbot [this message]
2025-10-25 13:35 ` Jens Axboe
2025-10-26 4:55 ` Chaitanya Kulkarni
2025-10-26 5:43 ` Chaitanya Kulkarni
2025-10-27 6:51 ` Johannes Thumshirn
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=68fcc036.a00a0220.9662e.0017.GAE@google.com \
--to=syzbot+153e64c0aa875d7e4c37@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.