Linux EXT4 FS development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Naman Jain" <namjain@linux.microsoft.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH 6.1] ext4: honor NULL returns from __filemap_get_folio()
Date: Mon, 02 Nov 2026 16:38:22 +0000	[thread overview]
Message-ID: <sashiko-outbox-193760@kernel.org> (raw)
In-Reply-To: <20261102163341.2170232-1-namjain@linux.microsoft.com>

> The bitmap and buddy folio conversions assume that
> __filemap_get_folio() returns error pointers. In Linux 6.1, however,
> it returns NULL both when a non-creating lookup misses and when folio
> creation fails.
> 
> A cache miss therefore passes the IS_ERR() check and reaches
> folio_test_uptodate(NULL) in ext4_mb_load_buddy_gfp(). Creating-lookup
> failures can also dereference NULL in its slow paths and in
> ext4_mb_get_buddy_page_lock().
> 
> Restore NULL checks at all six lookup sites and return -ENOMEM when a
> creating lookup fails. Preserve the folio locking and migration checks
> without changing the global filemap API.
> 
> Fixes: d34e4fd4e73f ("ext4: convert bd_bitmap_page to bd_bitmap_folio")
> Fixes: 862483175d3d ("ext4: convert bd_buddy_page to bd_buddy_folio")
> Cc: stable@vger.kernel.org # 6.1.x
> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261102163341.2170232-1-namjain@linux.microsoft.com?part=1


  reply	other threads:[~2026-11-02 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 16:33 [PATCH 6.1] ext4: honor NULL returns from __filemap_get_folio() Naman Jain
2026-11-02 16:38 ` sashiko-bot [this message]
2026-11-02 17:09 ` Matthew Wilcox
2026-11-02 17:24   ` Naman Jain

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=sashiko-outbox-193760@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=namjain@linux.microsoft.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tytso@mit.edu \
    /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