linux-ext4 - Does `-O bigalloc` still conflict with `delalloc`?

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

Message-ID: <923065C9-2EFB-4F59-895E-139B4B9F9E98@amazon.com>
Date:   Sat, 21 May 2022 02:39:00 +0000
From:   "Kiselev, Oleg" <okiselev@...zon.com>
To:     "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
CC:     Theodore Ts'o <tytso@....edu>
Subject: Does `-O bigalloc` still conflict with `delalloc`?

The `ext4(5)` man page, contained in the most recent e2fsprogs still says:

	Warning: The bigalloc feature is still under development, and may not be fully  supported
              with your kernel or may have various bugs.  Please see the web page http://ext4.wiki.ker‐
              nel.org/index.php/Bigalloc for details.  May clash with delayed allocation (see  nodelal‐
              loc mount option).

Is a bad interaction with `delalloc` still an issue and should we be using the `nodelalloc` option?