linux-ext4 - Re: Reading inode..

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

Date:	Thu, 18 Sep 2008 15:36:16 -0600
From:	Andreas Dilger <adilger@....com>
To:	Rohit Sharma <imreckless@...il.com>
Cc:	ext4 <linux-ext4@...r.kernel.org>,
	Kernelnewbies <kernelnewbies@...linux.org>
Subject: Re: Reading inode..

On Sep 17, 2008  19:37 +0530, Rohit Sharma wrote:
> I want to read ext2 inode.
> 
> Its just like i have a inode no. say 1900..
> so from the block group we can read the group descriptor and from there we
> can identify the first block no. of the inode table.
> So we can read the required inode no.i.e. 1900 from this inode table.
> I found that there are 8176 inodes per block group using tune2fs utility,

That is true for your filesystem, it might be different for each ext*
filesystems, depending on many parameters.

> so if i am interested in reading 8177th inode then i have to move on
> to next block groups inode table.

Right, for this particular filesystem.

Note also that there is libext2fs for performing operations like this on
the filesystem in userspace.

If you are reading the inode from within the kernel you can just use
ext2_read_inode().

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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