From: syzbot <syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com>
To: brauner@kernel.org, chandan.babu@oracle.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, sunjunchao2870@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iomap?] [xfs?] WARNING in iomap_write_begin
Date: Sun, 01 Sep 2024 22:28:01 -0700 [thread overview]
Message-ID: <0000000000006156d606211c3444@google.com> (raw)
In-Reply-To: <20240902050455.474396-1-sunjunchao2870@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com
Tested-by: syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com
Tested on:
commit: ee9a43b7 Merge tag 'net-6.11-rc3' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1710c453980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9358cc4a2e37fd30
dashboard link: https://syzkaller.appspot.com/bug?extid=296b1c84b9cbf306e5a0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=14f2e529980000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2024-09-02 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 8:14 [syzbot] [iomap?] [xfs?] WARNING in iomap_write_begin syzbot
2024-08-27 8:54 ` Julian Sun
2024-08-27 10:13 ` Christoph Hellwig
2024-08-27 11:13 ` Julian Sun
2024-08-27 11:37 ` Christoph Hellwig
2024-08-27 11:40 ` Aleksandr Nogikh
2024-08-27 11:56 ` Julian Sun
2024-08-27 12:38 ` syzbot
2024-08-30 9:48 ` Julian Sun
2024-08-30 10:19 ` syzbot
2024-08-30 11:31 ` Julian Sun
2024-08-30 12:04 ` syzbot
2024-09-02 5:04 ` Julian Sun
2024-09-02 5:28 ` 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=0000000000006156d606211c3444@google.com \
--to=syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sunjunchao2870@gmail.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;
as well as URLs for NNTP newsgroup(s).