linux-ext4 - inline_data feature

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: <loom.20140122T171340-153@post.gmane.org>
Date:	Wed, 22 Jan 2014 16:17:06 +0000 (UTC)
From:	Ian Nartowicz <claws@...towicz.co.uk>
To:	linux-ext4@...r.kernel.org
Subject: inline_data feature

I have been trying to test the inline_data feature of EXT4.  I am using
kernel 3.9.5 and have compiled e2fsprogs from the pu branch.  I am able to
set the feature and apparently to use the filesystem, but I get a lot of
warnings from the kernel and fsck reports several errors and then crashes.

Typical kernel warnings from dmesg:
EXT4-fs warning (device sda10): ext4_rmdir:2714: empty directory has too
many links (9)
EXT4-fs error (device sda10): empty_inline_dir:1650: inode #26263: block
1924: comm pool: bad entry in directory: directory entry across range -
offset=40(40), inode=26270, rec_len=8020, name_len=2
EXT4-fs warning (device sda10): empty_inline_dir:1657: bad inline directory
(dir #26263) - inode 26270, rec_len 8020, name_len 2inline size 60

Data does appear to be correctly written and read from the filesystem
without corruption.  Small directories appear with size 60 bytes or 132
bytes rather than 4.1kB so everything seems to work.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html