From: Julian Sun <sunjunchao2870@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: syzbot <syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com>,
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, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iomap?] [xfs?] WARNING in iomap_write_begin
Date: Tue, 27 Aug 2024 19:13:57 +0800 [thread overview]
Message-ID: <9cf7d25751d18729d14eef077b58c431f2267e0f.camel@gmail.com> (raw)
In-Reply-To: <Zs2m1cXz2o8o1IC-@infradead.org>
On Tue, 2024-08-27 at 03:13 -0700, Christoph Hellwig wrote:
> On Tue, Aug 27, 2024 at 04:54:41PM +0800, Julian Sun wrote:
> > On Tue, 2024-08-13 at 01:14 -0700, syzbot wrote:
> > Hi,
> >
> > Is this still a valid problem, or is it a known issue? If it is
> > still
> > valid, I'd like to dig it into, but do you have any ideas or
> > suggestions before I proceed? Thanks.
>
> I tried to reproduce it locally but haven't hit it. Once reproduced
> the next debug check would be which of the need zeroing conditions
> triggers.
>
Hi Christoph, thanks for your reply.
Did you use the config and reproducer provided by syzbot? I can easily
reproduce this issue using the config and c reproducer provided by
syzbot.
Thanks,
--
Julian Sun <sunjunchao2870@gmail.com>
next prev parent reply other threads:[~2024-08-27 11:14 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 [this message]
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
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=9cf7d25751d18729d14eef077b58c431f2267e0f.camel@gmail.com \
--to=sunjunchao2870@gmail.com \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.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).