linux-ext4 - Too large value in inode.i

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:	Wed, 12 Jun 2013 05:08:21 +0000 (UTC)
From:	Felipe Monteiro de Carvalho <felipemonteiro.carvalho@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Too large value in inode.i_blocks[1]

Hello,

Continuing in my adventures with ext4, now I am having
a problem that when reading the root
inode everything is fine. 
When reading the inodes of directories placed on the file system root,
my reading fails, because inode.i_blocks has the following data 
(for 1 particular subdir for example):

127754,
4,
0,
0,
1,
1366,
0,...

The root works because in its inode i_blocks[1] has a smaller, 
in-bounds value, but this one has
the first value completely out of bounds of the filesystem =(

My ext4 filesystem has 3 incompat flags set: EXT4_FEATURE_INCOMPAT_FILETYPE,
EXT4_FEATURE_INCOMPAT_EXTENTS, EXT4_FEATURE_INCOMPAT_FLEX_BG

I suppose it must be related to either EXTENTS or FLEX_BG ...

any ideas?

Also, where can I read about the exact effect of ext4 new features?

thanks,

Felipe Monteiro de Carvalho

--
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