public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+53d541c7b07d55a392ca@syzkaller.appspotmail.com>
To: chandan.babu@oracle.com, djwong@kernel.org,
	linux-kernel@vger.kernel.org,  linux-xfs@vger.kernel.org,
	lizhi.xu@windriver.com,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_can_free_eofblocks (2)
Date: Sat, 14 Sep 2024 02:21:03 -0700	[thread overview]
Message-ID: <66e5557f.050a0220.175489.0004.GAE@google.com> (raw)
In-Reply-To: <20240914090051.636332-1-lizhi.xu@windriver.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+53d541c7b07d55a392ca@syzkaller.appspotmail.com
Tested-by: syzbot+53d541c7b07d55a392ca@syzkaller.appspotmail.com

Tested on:

commit:         b7718454 Merge tag 'pci-v6.11-fixes-4' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e18407980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=709406cf7915cc0e
dashboard link: https://syzkaller.appspot.com/bug?extid=53d541c7b07d55a392ca
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=134350a9980000

Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2024-09-14  9:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 12:35 [syzbot] [xfs?] possible deadlock in xfs_can_free_eofblocks (2) syzbot
2024-09-14  9:00 ` Lizhi Xu
2024-09-14  9:21   ` 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=66e5557f.050a0220.175489.0004.GAE@google.com \
    --to=syzbot+53d541c7b07d55a392ca@syzkaller.appspotmail.com \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --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