linux-ext4 - Re: Issue with ext4 filesystem corruption when writing to a file after disk exhaustion

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJxJ_jhYUqYhNcsLnjPv+2-n83G77zeQ1jppC6YGfo6bHv+vaA@mail.gmail.com>
Date: Fri, 11 Jul 2025 17:56:18 +0800
From: Jiany Wu <wujianyue000@...il.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: yi.zhang@...wei.com, jack@...e.cz, linux-ext4@...r.kernel.org
Subject: Re: Issue with ext4 filesystem corruption when writing to a file
 after disk exhaustion

Hello, Ted,

Thanks indeed for the help, really appreciated!
BTW, is it proper to fallocate whole disk space to exhaust disk?
I see even fallocate full disk size, seems file size equal to avail
size still can be allocated.
i.e. When /tmp availability space is 26G, but fallocate requests 32G
(total disk space), we see it finally allocated a 26G file, but exit
code is 1.
Is it legal usage or will it trigger some unknown issue? I'm a newbie
on fallocate:)

Best regards,
Jianyue Wu