linux-ext4 - Re: [Patch 0/2] Journal Checksums

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:	Wed, 30 May 2007 16:06:40 +0530
From:	Girish Shilamkar <girish@...sterfs.com>
To:	linux-ext4@...r.kernel.org
Cc:	Andreas Dilger <adilger@...sterfs.com>
Subject: Re: [Patch 0/2] Journal Checksums

Hi,
	I forgot mention, this patch is spinoff of patch originally written by
Vijayan Prabhakaran.

Thanks & Regards.
Girish

On Wed, 2007-05-30 at 16:01 +0530, Girish Shilamkar wrote:
> Hi,
>  	The following patch set adds journal checksumming support for linux
> kernel and e2fsprogs. 
> 
> Two new flags have been added i.e 
> JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT and JBD2_FEATURE_COMPAT_CHECKSUM.
> 
> _CHECKSUM flag indicates that the commit block contains the checksum for
> the blocks described the the descriptor blocks.
> Due to checksums, writing of the commit record no longer needs to be
> synchronous, this behavior is controlled using _ASYNC_COMMIT flag. Older
> kernels/e2fsck should not be able to recover the journal with
> _ASYNC_COMMIT hence it is made incompat. 
> The commit header has been extended to hold the checksum along with the
> type of the checksum.
> 
> For recovery in pass scan checksums are verified to ensure the sanity
> and completeness(in case of _ASYNC_COMMIT) of every transaction.
> 
> Any suggestions/comments are welcome.
> 
> Thanks & Regards,
> Girish.
> 
> 
> 

-
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