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

Hello,

Theodore Ts'o <tytso <at> mit.edu> writes:
> The inode in question has the EXTENTS_FL flag set, which means the
> i_blocks[] array needs to get interpreted as the root node of the
> extent tree. 127754 is 0x0001F30A, where F30A is the magic number for
> the extents header, and 0x0001 means there is a single entry in the
> extent node.

Thanks, great =) So reading 
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#The_Contents_of_inod
e.i_block

I see that i_block has 15*4=60 bytes, and with EXTENTS_FL the first 12 bytes 
of i_block are filled with a ext4_extent_header

What about the rest of it? I couldn't understand from the wiki page what
the rest holds exactly, it is not 100% clear ...

My first guess would be that it has in this order:

ext4_extent_header, 12 bytes long
ext4_extent_idx, 12 bytes long:
ext4_extent, 12 bytes long
ext4_extent_tail 4 bytes long

Which would sum 40 bytes ... still unsure about the other 20 however.

Any help here is greatly appreciated =)

> I **strongly** discourage people from trying to access the file system
> directly.  It's much better to use the libext2fs library, since it
> will deal with these sorts of issues for you automatically.  A

Please don't worry that I am not frivolously attempting to access the
file system directly. My project explictly requires this, it is a
recovery tool to repair damaged file systems, and it must work in
Windows and Mac OS X. Maybe libext2fs works outside Linux, not sure, 
but anyway we already have source code for reading/recovering ext2/3, 
I am just expanding it to ext4. External dependencies are always
not ideal.

I am new in the project, that's why I have so many beginner questions,
I appologise for it, but I'm thankful that I experienced developers 
like you answer them so that I can learn about the Linux Ext4
file system.

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

Powered by blists - more mailing lists