[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176962347637.1138505.14003201012666831144.b4-ty@mit.edu>
Date: Wed, 28 Jan 2026 13:05:01 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4@...r.kernel.org, libaokun@...weicloud.com
Cc: "Theodore Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca, jack@...e.cz,
linux-kernel@...r.kernel.org, yi.zhang@...wei.com,
yangerkun@...wei.com, libaokun1@...wei.com
Subject: Re: [PATCH] ext4: move ext4_percpu_param_init() before ext4_mb_init()
On Tue, 09 Dec 2025 21:31:16 +0800, libaokun@...weicloud.com wrote:
> When running `kvm-xfstests -c ext4/1k -C 1 generic/383` with the
> `DOUBLE_CHECK` macro defined, the following panic is triggered:
>
> ==================================================================
> EXT4-fs error (device vdc): ext4_validate_block_bitmap:423:
> comm mount: bg 0: bad block bitmap checksum
> BUG: unable to handle page fault for address: ff110000fa2cc000
> PGD 3e01067 P4D 3e02067 PUD 0
> Oops: Oops: 0000 [#1] SMP NOPTI
> CPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W
> 6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none)
> RIP: 0010:percpu_counter_add_batch+0x13/0xa0
> Call Trace:
> <TASK>
> ext4_mark_group_bitmap_corrupted+0xcb/0xe0
> ext4_validate_block_bitmap+0x2a1/0x2f0
> ext4_read_block_bitmap+0x33/0x50
> mb_group_bb_bitmap_alloc+0x33/0x80
> ext4_mb_add_groupinfo+0x190/0x250
> ext4_mb_init_backend+0x87/0x290
> ext4_mb_init+0x456/0x640
> __ext4_fill_super+0x1072/0x1680
> ext4_fill_super+0xd3/0x280
> get_tree_bdev_flags+0x132/0x1d0
> vfs_get_tree+0x29/0xd0
> vfs_cmd_create+0x59/0xe0
> __do_sys_fsconfig+0x4f6/0x6b0
> do_syscall_64+0x50/0x1f0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
> ==================================================================
>
> [...]
Applied, thanks!
[1/1] ext4: move ext4_percpu_param_init() before ext4_mb_init()
commit: 270564513489d98b721a1e4a10017978d5213bff
Best regards,
--
Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists