linux-kernel - Re: [Bug #14354] Bad corruption with 2.6.32-rc1 and upwards

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091118001142.GA3816@thunk.org>
Date:	Tue, 17 Nov 2009 19:11:42 -0500
From:	tytso@....edu
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	Frank Mayhar <fmayhar@...gle.com>,
	Holger Freyther <zecke@...fish.org>
Subject: Re: [Bug #14354] Bad corruption with 2.6.32-rc1 and upwards

On Tue, Nov 17, 2009 at 11:23:11PM +0100, Rafael J. Wysocki wrote:
> 
> I wasn't quite sure what the status was, because there was some
> activity in the bug entry after it had been marked as resolved.

Yeah, the actual regression had been resolved (by changing the
default), but the root cause was due to the fact that not enough
people had done proper power-fail testing for the journal_checksum,
even though the code had been in the kernel for a very long time.  The
discussion afterwards was focused around fixing those problems so we
could make journal_checksum be the default at some point in the future.

      	   		       	   	      - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/