From: Christoph Hellwig <hch@infradead.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
syzbot <syzbot+3735a85c5c610415e2b6@syzkaller.appspotmail.com>,
cem@kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] WARNING: kmalloc bug in xfs_buf_alloc
Date: Mon, 24 Nov 2025 00:46:25 -0800 [thread overview]
Message-ID: <aSQbYfHTBvX6cpsx@infradead.org> (raw)
In-Reply-To: <CANp29Y700kguy+8=9t7zG2NWZDYtgxfqkUqsRmE+C6_hFdh73g@mail.gmail.com>
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@infradead.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?
next prev parent reply other threads:[~2025-11-24 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 5:08 [syzbot] [xfs?] WARNING: kmalloc bug in xfs_buf_alloc syzbot
2025-11-24 7:10 ` Christoph Hellwig
2025-11-24 8:43 ` Aleksandr Nogikh
2025-11-24 8:46 ` Christoph Hellwig [this message]
2025-11-24 10:42 ` Aleksandr Nogikh
2025-11-24 14:01 ` Christoph Hellwig
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=aSQbYfHTBvX6cpsx@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+3735a85c5c610415e2b6@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