From: syzbot <syzbot+4125a3c514e3436a02e6@syzkaller.appspotmail.com>
To: cem@kernel.org, chandan.babu@oracle.com, djwong@kernel.org,
hch@infradead.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] KASAN: null-ptr-deref Write in xfs_filestream_select_ag (2)
Date: Tue, 22 Oct 2024 03:11:03 -0700 [thread overview]
Message-ID: <67177a37.050a0220.1e4b4d.0074.GAE@google.com> (raw)
In-Reply-To: <ZxdzTL4UYZtgsIiK@infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4125a3c514e3436a02e6@syzkaller.appspotmail.com
Tested-by: syzbot+4125a3c514e3436a02e6@syzkaller.appspotmail.com
Tested on:
commit: 0338c38c xfs: fix finding a last resort AG in xfs_file..
git tree: git://git.infradead.org/users/hch/misc.git xfs-filesystems-pick-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=11150287980000
kernel config: https://syzkaller.appspot.com/x/.config?x=41330fd2db03893d
dashboard link: https://syzkaller.appspot.com/bug?extid=4125a3c514e3436a02e6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2024-10-22 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 19:00 [syzbot] [xfs?] KASAN: null-ptr-deref Write in xfs_filestream_select_ag (2) syzbot
2024-10-20 2:53 ` Edward Adam Davis
2024-10-20 3:14 ` syzbot
2024-10-20 3:35 ` Edward Adam Davis
2024-10-20 4:12 ` syzbot
2024-10-20 5:00 ` Edward Adam Davis
2024-10-20 5:27 ` syzbot
2024-10-20 5:30 ` [PATCH] xfs: If unable to pick perag an error needs to be returned Edward Adam Davis
2024-10-21 13:51 ` Dave Chinner
2024-10-22 9:41 ` [syzbot] [xfs?] KASAN: null-ptr-deref Write in xfs_filestream_select_ag (2) Christoph Hellwig
2024-10-22 10:11 ` 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=67177a37.050a0220.1e4b4d.0074.GAE@google.com \
--to=syzbot+4125a3c514e3436a02e6@syzkaller.appspotmail.com \
--cc=cem@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@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