Re: [PATCH] ext4: use a stable source for the kmmpd thread name
From: Jan Kara
Date: Wed Nov 18 2026 - 06:15:55 EST
Hello,
On Tue 17-11-26 00:36:50, Zhao Gongyi wrote:
> On 11/16/26 8:16 PM, Jan Kara wrote:
> > What can change it? I don't see anything that should be doing that...
>
> A concurrent buffered write to the loop block device can change it. In
> one diagnostic run, the write reached the page-cache buffer ext4 was
> using for MMP. mmp_bdevname is embedded at bh->b_data + 0x50.
Ah, I see. So you're corrupting the filesystem through the block device
while it is mounted.
> I understand that raw writes to a block device during ext4 access can
> corrupt metadata. The proposed change gives the two-pass thread-name
> formatting a stable source; it does not change MMP's protection logic.
> I can provide the full diagnostic diff, kprobe module, and console log
> if useful.
Yes, sorry, but this isn't really something we care about. It is in
principle very similar as corrupting memory through /dev/mem and the
filesystem can crash in many different ways. When you are fuzzing, you
should disable BLK_DEV_WRITE_MOUNTED config which will also disallow
corruption like this.
Honza
--
Jan Kara <jack@xxxxxxxx>
SUSE Labs, CR