Re: [syzbot] [xfs?] WARNING: kmalloc bug in xfs_buf_alloc

[Aleksandr Nogikh]

On Mon, Nov 24, 2025 at 9:46 AM Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
>
> On Mon, Nov 24, 2025 at 09:43:47AM +0100, Aleksandr Nogikh wrote:
> > On Mon, Nov 24, 2025 at 8:10 AM Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> > >
> > > This got fixed in vmalloc by adding GFP_NOLOCKDEP to the allow vmalloc
> > > flags.
> > >
> > > Is syzbot now also running on linux-next?
> > >
> >
> > Linux-next has been one of the targets for a very long time already.
>
> Ok, I'm not updatodate then.  How do we deal with the fact that no
> specific commit fixed an issue, but a commit causing a problem got
> replaced with a different one in linux-next?

That's indeed a difficult question within our current bug tracking
model. For now, the best option would be to just invalidate the report
so that it does not stay open:
#syz invalid

We have a backlog issue regarding selecting a better approach:
https://github.com/google/syzkaller/issues/1878