linux-ext4 - ext2fs_test_block_bitmap (): Unknown code ext2 47 #0, etc.

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

Date:	Thu, 18 Aug 2011 23:27:30 +0700
From:	Ivan Shmakov <ivan@...y.siamics.net>
To:	linux-ext4@...r.kernel.org
Subject: ext2fs_test_block_bitmap (): Unknown code ext2 47 #0, etc.

>>>>> Ivan Shmakov <ivan@...y.siamics.net> writes:

[…]

 > (The support for the whole-image and metadata message digests is not
 > yet committed.)

	The code is now ready to be committed.  However, I'm getting the
	following message on stderr upon a call (only the first one?) to
	ext2fs_test_block_bitmap ():

--cut--
Unknown code ext2 47 #0 for block bitmap for /dev/stdin
--cut--

	Otherwise, e2dis seems to behave sanely.

	Also, do I understand it correctly that I need to call
	ext2fs_read_block_bitmap () before accessing the block_map
	member of the ext2_filsys structure?

[…]

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