linux-ext4 - 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-next>] [day] [month] [year] [list]

Message-ID: <382524.16755.qm@web43505.mail.sp1.yahoo.com>
Date:	Fri, 15 May 2009 13:49:38 -0700 (PDT)
From:	number9652@...oo.com
To:	linux-ext4@...r.kernel.org
Subject: e2fsprogs bmap problem

I am running into a problem with the output of the function ext2fs_bmap in the ext2fs library version 1.41.5: when I send it an inode structure pointer as the third argument and the number of a deleted inode as the second argument, it seems to end up trying to read the deleted inode from disk (and results in the returned value block number being 0), when I expected it to just get the values from the inode structure I send to it.  This only happens if the inode contains an extent structure within it; when it has the indirect block structure it behaves as I expected.

I couldn't find the documentation for this function, so is this the right behavior for this function?  If so, is there a better way to retrieve the block numbers pointed to by an inode structure provided by the ext2fs library?

Thanks,
N

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