linux-kernel - Re: [PATCH] ext4: implement filesystem specific alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cdeaa9ac-b3aa-4951-9c34-4b4ae71df89d@roeck-us.net>
Date: Sat, 27 Apr 2024 12:09:45 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Kemeng Shi <shikemeng@...weicloud.com>
Cc: tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext4: implement filesystem specific alloc_inode in unit
 test

Hi,

On Sat, Mar 23, 2024 at 12:55:18AM +0800, Kemeng Shi wrote:
> We expect inode with ext4_info_info type as following:
> mbt_kunit_init
>   mbt_mb_init
>     ext4_mb_init
>       ext4_mb_init_backend
>         sbi->s_buddy_cache = new_inode(sb);
>         EXT4_I(sbi->s_buddy_cache)->i_disksize = 0;
> 
> Implement alloc_inode ionde with ext4_inode_info type to avoid
> out-of-bounds write.
> 
> Signed-off-by: Kemeng Shi <shikemeng@...weicloud.com>
> Reported-by: Guenter Roeck <linux@...ck-us.net>
> ---

Ths problem fixed by this patch still affects the mainline kernel,
and is often fatal there if CONFIG_EXT4_KUNIT_TESTS is enabled
due to memory corruptions. Is there a chance to get it applied soon,
or should I just disable CONFIG_EXT4_KUNIT_TESTS for good ?

Thanks,
Guenter