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: Mon, 03 Feb 2025 00:36:02 -0800 [thread overview]
Message-ID: <67a07ff2.050a0220.163cdc.003e.GAE@google.com> (raw)
In-Reply-To: <20250203080720.GA18459@lst.de>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+acb56162aef712929d3f@syzkaller.appspotmail.com
Tested-by: syzbot+acb56162aef712929d3f@syzkaller.appspotmail.com
Tested on:
commit: 2014c95a Linux 6.14-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=10fa43df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=793f583a4388e6da
dashboard link: https://syzkaller.appspot.com/bug?extid=acb56162aef712929d3f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12b3b5f8580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-02-03 8:36 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
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 [this message]
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=67a07ff2.050a0220.163cdc.003e.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