linux-ext4 - Re: e2fsprogs bmap problem

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:	Mon, 18 May 2009 12:32:06 -0400
From:	Theodore Tso <tytso@....edu>
To:	number9652 <number9652@...oo.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: e2fsprogs bmap problem

On Mon, May 18, 2009 at 07:56:38AM -0700, number9652 wrote:
> 
> I have looked at it a little more closely now, and to me it seems
> that we could add a new function like ext2fs_extent_open to accept
> an inode structure, as an alternative to changing the extent
> structure.

Yes, the right way to do this is to create a new function,
ext2fs_extent_open2() which takes a new parameter, struct inode
*inode, and then make ext2fs_extent_open() call ext2fs_extent_open2()
with the inode parameter set to NULL.  In ext2fs_extent_open2(), if
struct inode *inode is non-NULL, then we use it instead of reading in
the inode.  The one tricky bit is that we will need to use
ext2fs_read_inode() and ext2fs_write_inode() instead of
ext2fs_read_inode_full()/ext2fs_write_inode_full(), but that's OK; the
extents code didn't really need to pull in the full inode structure
anyway.

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