linux-ext4 - ext2fs_block_iterate (e2, EXT2_RESIZE_INO, ...) => EXT2_ET_FILE_TOO

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: <867h5tdf9o.fsf@gray.siamics.net>
Date:	Wed, 31 Aug 2011 17:52:35 +0700
From:	Ivan Shmakov <ivan@...y.siamics.net>
To:	linux-ext4@...r.kernel.org
Subject: ext2fs_block_iterate (e2, EXT2_RESIZE_INO, ...) => EXT2_ET_FILE_TOO_BIG? 

	Curiosly enough, ext2fs_block_iterate () returns
	EXT2FS_BLOCK_ITERATE for EXT2_RESIZE_INO (the binary in question
	is statically linked against libext2fs, 1.41.12 debian 2):

(gdb) print ext2fs_block_iterate (e2, ino, 0, 0, db_add_block, (void *)sp)
$13 = 2133571410
(gdb) 

	Is it because the blocks belonging to this inode aren't supposed
	to belong to the filesystem itself, I wonder?

	TIA.

-- 
FSF associate member #7257	Coming soon: Software Freedom Day
http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en)

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