linux-ext4 - Re: [PATCH 12/18] e2fsck: toggle checksum verification error reporting appropriately

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]

Message-ID: <20140728114108.GL6725@thunk.org>
Date:	Mon, 28 Jul 2014 07:41:08 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 12/18] e2fsck: toggle checksum verification error
 reporting appropriately

On Mon, Jul 28, 2014 at 12:38:26AM -0700, Darrick J. Wong wrote:
> 
> We could make e2fsck verify the checksums itself, though we'd have to provide a
> way for either (a) libext2fs to provide the raw buffer data to e2fsck or (b)
> e2fsck to find the block number in question and (re)read the raw buffer, since
> the checksums are computed against the on-disk structures.

Hmm.  Another possibility is we could change the functions so that if
there is a checksum error, we return the error code, but we also
return the contents of the inode, directory entry, etc. to the caller.

       	   	       	   	  	    	   - 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