[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0bdaf103f5f8de02a48b33481f787c4ac8806df5.camel@gmail.com>
Date: Tue, 27 Aug 2024 19:56:23 +0800
From: Julian Sun <sunjunchao2870@...il.com>
To: Aleksandr Nogikh <nogikh@...gle.com>, Christoph Hellwig
<hch@...radead.org>
Cc: syzbot <syzbot+296b1c84b9cbf306e5a0@...kaller.appspotmail.com>,
brauner@...nel.org, chandan.babu@...cle.com, djwong@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [iomap?] [xfs?] WARNING in iomap_write_begin
On Tue, 2024-08-27 at 13:40 +0200, Aleksandr Nogikh wrote:
> On Tue, Aug 27, 2024 at 1:37 PM Christoph Hellwig <hch@...radead.org>
> wrote:
> >
> > On Tue, Aug 27, 2024 at 07:13:57PM +0800, Julian Sun wrote:
> > > 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.
> >
> > I used the reproducer on my usual test config for a quick run.
> > I'll try the syzcaller config when I get some time.
>
> FWIW if you just want to check if the bug is still present in the
> kernel tree, you can ask syzbot to build the latest revision and run
> the reproducer there.
>
> #syz test
Thanks for the remainder, I will try it.
Thanks,
--
Julian Sun <sunjunchao2870@...il.com>
Powered by blists - more mailing lists