linux-ext4 - Re: [PATCH] ext4/048: Fix hangup due to no free inodes

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <7bb8d73b-6394-4cb2-9e36-76cfbd584a76@huawei.com>
Date: Tue, 28 Oct 2025 19:34:34 +0800
From: Baokun Li <libaokun1@...wei.com>
To: Ojaswin Mujoo <ojaswin@...ux.ibm.com>
CC: Zorro Lang <zlang@...hat.com>, <fstests@...r.kernel.org>, Leah Rumancik
	<lrumancik@...gle.com>, <linux-ext4@...r.kernel.org>, Yang Erkun
	<yangerkun@...wei.com>
Subject: Re: [PATCH] ext4/048: Fix hangup due to no free inodes

On 2025-10-28 17:39, Ojaswin Mujoo wrote:
> On Tue, Oct 28, 2025 at 03:57:00PM +0800, Baokun Li wrote:
>> On 2025-10-28 15:17, Ojaswin Mujoo wrote:
>>> We currently mkfs a 128MB filesystem, which gives use ~2048 free inodes
>>> on 64k blocksize. The test then keeps adding new files to a directory to
>>> trigger an htree split. For 64k this takes more than the total free
>>> inodes, which causes touch to return -ENOSPC. This leads to the while
>>> loop in induce_node_split() to never finish.
>>>
>>> To fix this:
>>> 1. Format a 1G FS which gives us atleast 16K inodes to work with.
>>> 2. _fail if there's any error while trying to induce node split, so we
>>>    dont get stuck in loop
>>>
>>> Fixes: 466ddbfd1151 ("ext4: add test for ext4_dir_entry2 wipe")
>>> Signed-off-by: Ojaswin Mujoo <ojaswin@...ux.ibm.com>
>>> ---
>> Yeah, I also hit this issue when testing LBS — file creation kept failing
>> without breaking out of the loop, which resulted in the test case spinning
>> endlessly.
>>
>> Looks good to me. Feel free to add:
>>
>> Reviewed-by: Baokun Li <libaokun1@...wei.com>
> Hi Baokun, I was planning to CC you since I thought you might've hit it,
> but missed it while sending the mail.

No worries, the mailing list can see it as well.

Thanks for testing and fixing this. 🤝


Cheers,
Baokun