All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info
@ 2026-08-04  4:55 Junzhe Yu
  2026-08-06 14:35 ` Theodore Tso
  2026-08-06 15:00 ` Theodore Ts'o
  0 siblings, 2 replies; 3+ messages in thread
From: Junzhe Yu @ 2026-08-04  4:55 UTC (permalink / raw)
  To: Theodore Ts'o, Andreas Dilger; +Cc: linux-ext4, linux-kernel

Resend: previous attempt was rejected by vger for containing HTML.

==================================================================

ext4_mark_group_bitmap_corrupted() already treats a NULL return from
ext4_get_group_info() as "nothing to do", but ext4_get_group_info()
indexes s_group_info without checking whether the array exists.

During mount, fast-commit replay runs inside jbd2_journal_load() from
ext4_load_and_init_journal(), which is before ext4_mb_init() allocates
s_group_info. Replaying an FC UNLINK for an inode whose bitmap bit is
already clear takes:

   ext4_fc_replay_unlink -> iput -> ext4_evict_inode -> ext4_free_inode
     -> ext4_mark_group_bitmap_corrupted -> ext4_get_group_info

and faults on the NULL s_group_info base. Userspace only mounts a dirty
ext4 image; this is a supported recovery path.

Return NULL when s_group_info (or the per-block grp_info row) is unset
so the existing caller check is effective during early mount.

Tested on Linux v6.6.145 KASAN: crafted FC-unlink image previously
triggered KASAN null-ptr-deref / panic in ext4_get_group_info; with this
patch, mount succeeds (EXT4 "bit already cleared" may still log). Also
observed on v6.6.144; still present on torvalds/linux as of
f5098b6bae76 (2026-07-26).

A self-contained Docker/QEMU reproducer (craft + mount + patch verify) is
available on request.

Signed-off-by: Yu Junzhe <junzheyu1@gmail.com>
---
  fs/ext4/balloc.c | 4 ++++
  1 file changed, 4 insertions(+)

diff --git a/fs/ext4/balloc.c b/fs/ext4/balloc.c
index 3a2dfc5..80c81bc 100644
--- a/fs/ext4/balloc.c
+++ b/fs/ext4/balloc.c
@@ -329,9 +329,13 @@ struct ext4_group_info *ext4_get_group_info(struct 
super_block *sb,

      if (unlikely(group >= EXT4_SB(sb)->s_groups_count))
          return NULL;
+    if (unlikely(!EXT4_SB(sb)->s_group_info))
+        return NULL;
      indexv = group >> (EXT4_DESC_PER_BLOCK_BITS(sb));
      indexh = group & ((EXT4_DESC_PER_BLOCK(sb)) - 1);
      grp_info = sbi_array_rcu_deref(EXT4_SB(sb), s_group_info, indexv);
+    if (unlikely(!grp_info))
+        return NULL;
      return grp_info[indexh];
  }

-- 
2.53.0



^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info
  2026-08-04  4:55 [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info Junzhe Yu
@ 2026-08-06 14:35 ` Theodore Tso
  2026-08-06 15:00 ` Theodore Ts'o
  1 sibling, 0 replies; 3+ messages in thread
From: Theodore Tso @ 2026-08-06 14:35 UTC (permalink / raw)
  To: Junzhe Yu; +Cc: Andreas Dilger, linux-ext4, linux-kernel

On Tue, Aug 04, 2026 at 12:55:33PM -0500, Junzhe Yu wrote:
> Resend: previous attempt was rejected by vger for containing HTML.

This attempt still had a patch with mangled whitespace.  Trying to
send patches using gmail is... fraught.  Please a take a look at [1]
for future submissions, thanks.  This patch was simple enough that I
was able to apply it by hand.

[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html

						- Ted

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info
  2026-08-04  4:55 [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info Junzhe Yu
  2026-08-06 14:35 ` Theodore Tso
@ 2026-08-06 15:00 ` Theodore Ts'o
  1 sibling, 0 replies; 3+ messages in thread
From: Theodore Ts'o @ 2026-08-06 15:00 UTC (permalink / raw)
  To: Andreas Dilger, Junzhe Yu; +Cc: Theodore Ts'o, linux-ext4, linux-kernel


On Tue, 04 Aug 2026 12:55:33 +0800, Junzhe Yu wrote:
> Resend: previous attempt was rejected by vger for containing HTML.
> 
> ==================================================================
> 
> ext4_mark_group_bitmap_corrupted() already treats a NULL return from
> ext4_get_group_info() as "nothing to do", but ext4_get_group_info()
> indexes s_group_info without checking whether the array exists.
> 
> [...]

Applied, thanks!

[1/1] ext4: guard against NULL s_group_info in ext4_get_group_info
      commit: 8f3901fbb40745046e513226ad84e8b84492632d

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-08-06 15:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-04  4:55 [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info Junzhe Yu
2026-08-06 14:35 ` Theodore Tso
2026-08-06 15:00 ` Theodore Ts'o

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.