linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com>
To: cem@kernel.org, hch@infradead.org, linux-kernel@vger.kernel.org,
	 linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc
Date: Wed, 03 Sep 2025 01:25:02 -0700	[thread overview]
Message-ID: <68b7fb5e.050a0220.3db4df.01e8.GAE@google.com> (raw)
In-Reply-To: <aLfal0B4HnWJVWz1@infradead.org>

Hello,

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

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

Tested on:

commit:         e6b9dce0 Merge tag 'sound-6.17-rc5' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145aee62580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=39f8a155475bc42d
dashboard link: https://syzkaller.appspot.com/bug?extid=ab02e4744b96de7d3499
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2025-09-03  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  1:51 [syzbot] [xfs?] WARNING in xfs_trans_alloc syzbot
2025-08-18  4:40 ` Christoph Hellwig
2025-08-30 18:03 ` syzbot
2025-09-03  6:04   ` Christoph Hellwig
2025-09-03  6:04     ` syzbot
2025-09-03  6:05       ` Christoph Hellwig
2025-09-03  8:25         ` 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=68b7fb5e.050a0220.3db4df.01e8.GAE@google.com \
    --to=syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com \
    --cc=cem@kernel.org \
    --cc=hch@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).