Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-ext4@vger.kernel.org, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	"Safe-Lock.NET Dawid Partyka" <internet.jejkowice@gmail.com>
Subject: Re: [REGRESSION] 6.1.192: NULL deref in ext4_mb_load_buddy_gfp() after, dropping page cache (__filemap_get_folio() returns NULL, callers check IS_ERR())
Date: Fri, 20 Nov 2026 15:39:18 -0500	[thread overview]
Message-ID: <2026-11-20-1-daily-reply-0029@kernel.org> (raw)
In-Reply-To: <81b3f525-0d62-4a46-a0f3-77d54b11d847@gmail.com>

> After updating from 6.1.190 to 6.1.192 I get a reproducible NULL pointer
> dereference in ext4_mb_load_buddy_gfp() whenever the buddy/bitmap pages of
> an ext4 group are not in the page cache.

The fix, "ext4: fix NULL folio dereference in mballoc", is queued and is in
6.1.193-rc2.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-20 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  8:15 [REGRESSION] 6.1.192: NULL deref in ext4_mb_load_buddy_gfp() after, dropping page cache (__filemap_get_folio() returns NULL, callers check IS_ERR()) Safe-Lock.NET Dawid Partyka
2026-11-20 20:39 ` Sasha Levin [this message]

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=2026-11-20-1-daily-reply-0029@kernel.org \
    --to=sashal@kernel.org \
    --cc=internet.jejkowice@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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