From: syzbot <syzbot+acb56162aef712929d3f@syzkaller.appspotmail.com>
To: cem@kernel.org, chandan.babu@oracle.com, djwong@kernel.org,
hch@lst.de, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_buf_find_insert
Date: Sun, 02 Feb 2025 07:08:03 -0800 [thread overview]
Message-ID: <679f8a53.050a0220.d7c5a.0070.GAE@google.com> (raw)
In-Reply-To: <6798b182.050a0220.ac840.0248.GAE@google.com>
syzbot has bisected this issue to:
commit ee10f6fcdb961e810d7b16be1285319c15c78ef6
Author: Christoph Hellwig <hch@lst.de>
Date: Thu Jan 16 06:01:42 2025 +0000
xfs: fix buffer lookup vs release race
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1193ad18580000
start commit: 69b8923f5003 Merge tag 'for-linus-6.14-ofs4' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1393ad18580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1593ad18580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57ab43c279fa614d
dashboard link: https://syzkaller.appspot.com/bug?extid=acb56162aef712929d3f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174cd5f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162e2d18580000
Reported-by: syzbot+acb56162aef712929d3f@syzkaller.appspotmail.com
Fixes: ee10f6fcdb96 ("xfs: fix buffer lookup vs release race")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-02 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xUgzg-Ms26GwUwJb_y_dH4Cd0_wpb0bHNZThgjgF0jAZyXDNjGasYRqOCgqPHOnBgRMUpwFAPpzdPoRfPXcn4Q==@protonmail.internalid>
2025-01-28 10:29 ` [syzbot] [xfs?] possible deadlock in xfs_buf_find_insert syzbot
2025-01-28 10:36 ` Carlos Maiolino
2025-01-28 10:37 ` syzbot
2025-02-02 0:53 ` syzbot
2025-02-02 15:08 ` syzbot [this message]
2025-02-03 7:30 ` Christoph Hellwig
2025-02-03 7:55 ` syzbot
2025-02-03 8:07 ` Christoph Hellwig
2025-02-03 8:36 ` syzbot
2025-03-14 16:19 ` syzbot
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=679f8a53.050a0220.d7c5a.0070.GAE@google.com \
--to=syzbot+acb56162aef712929d3f@syzkaller.appspotmail.com \
--cc=cem@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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