linux-ext4 - inline_data status (e2fsprogs)

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]

Date:   Sat, 14 Sep 2019 20:06:04 +0200
From:   Pas <pas@...g.hu>
To:     linux-ext4@...r.kernel.org
Subject: inline_data status (e2fsprogs)

Hello,

I hope this is the correct forum to ask these questions. (If not, then
sorry for the noise! Though then could you recommend where to ask
them?)

Is there any reason that inline_data is not a default enabled feature?
(The default inode size is already 256.
https://github.com/tytso/e2fsprogs/blob/dc5433647cb79bf1e7660f441c64330b3b8757cc/misc/mke2fs.conf.in#L14
)

Also, any particular reason that tune2fs cannot enable this feature?
("Setting filesystem feature 'inline_data' not supported.")

Finally, what are the dangers of using debugfs to enable the feature
flag? (As suggested here https://unix.stackexchange.com/a/309260/4003
)

Thanks,
Pas