From: syzbot <syzbot+bd975ef54294bec73f0e@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bvanassche@acm.org, hch@lst.de,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
mzx199711@gmail.com, sunjunchao@bytedance.com,
syzkaller-bugs@googlegroups.com, tz2294@columbia.edu
Subject: Re: [syzbot] [block?] possible deadlock in blkdev_buffered_write
Date: Mon, 26 Oct 2026 17:17:04 -0700 [thread overview]
Message-ID: <6adfed80.6200f071.51519.0efd.GAE@google.com> (raw)
In-Reply-To: <6ad78978.b5bd089a.6b57.008d.GAE@google.com>
syzbot has bisected this issue to:
commit 1b1be9ea4e34ccede1e7cf9ff2b6317328a5b6ad
Author: Julian Sun <sunjunchao@bytedance.com>
Date: Thu Oct 15 09:11:05 2026 +0000
block: take the inode lock for buffered write fallback
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=165121e1580000
start commit: 21a7f44fd076 Merge tag 'devicetree-for-7.4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=155121e1580000
console output: https://syzkaller.appspot.com/x/log.txt?x=115121e1580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb217ea80b9f9fe
dashboard link: https://syzkaller.appspot.com/bug?extid=bd975ef54294bec73f0e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1634b469580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108dd695580000
Reported-by: syzbot+bd975ef54294bec73f0e@syzkaller.appspotmail.com
Fixes: 1b1be9ea4e34 ("block: take the inode lock for buffered write fallback")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-10-27 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:32 [syzbot] [block?] possible deadlock in blkdev_buffered_write syzbot
2026-10-27 0:17 ` 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=6adfed80.6200f071.51519.0efd.GAE@google.com \
--to=syzbot+bd975ef54294bec73f0e@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mzx199711@gmail.com \
--cc=sunjunchao@bytedance.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tz2294@columbia.edu \
/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.