linux-kernel - Re: [syzbot] [xfs?] WARNING: kmalloc bug in xfs_buf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANp29Y4qahxvc3MDUQi6ScTK-RVnbTSL3C4TGYPZampEpXKWNA@mail.gmail.com>
Date: Mon, 24 Nov 2025 11:42:07 +0100
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: syzbot <syzbot+3735a85c5c610415e2b6@...kaller.appspotmail.com>, cem@...nel.org, 
	linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [xfs?] WARNING: kmalloc bug in xfs_buf_alloc

On Mon, Nov 24, 2025 at 9:46 AM Christoph Hellwig <hch@...radead.org> 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@...radead.org> 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