linux-kernel - Re: hunt for 2.6.37 dm-crypt+ext4 corruption?

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]

Date:	Sun, 5 Dec 2010 16:15:02 -0500
From:	Mike Snitzer <snitzer@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Theodore Tso <tytso@....EDU>,
	device-mapper development <dm-devel@...hat.com>,
	Heinz Diehl <htd@...tha.org>, Jon Nelson <jnelson@...poni.net>,
	htejun@...il.com, Matt <jackdachef@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Chris Mason <chris.mason@...cle.com>,
	htd <htd@...cy-poultry.org>, linux-ext4@...r.kernel.org,
	linux-btrfs <linux-btrfs@...r.kernel.org>
Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption?

On Sun, Dec 05 2010 at  3:28pm -0500,
Andi Kleen <andi@...stfloor.org> wrote:

> > As another thought, what version of GCC are people using who are having difficulty?   Could this perhaps be a compiler-related issue?
> 
> A compiler problem seems very unlikely here.
> 
> What may be an useful experiment would be to test 2.6.37-rc + ext4 over
> device mapper, but not dmcrypt. If that fails too then it's likely
> some generic device mapper problem.

That would only prove its not dm-crypt; it would not absolve a non-DM
2.6.37-rc change at all.

Leveraging the fact that 2.6.36 + parallel dm-crypt is reportedly very
solid: maybe these would be more interesting (each would keep the latest
parallel dm-crypt patch overlayed for all tests):

1) Test 2.6.37-rc prior to all flush+fua changes (only changes DM saw
   for 2.6.37-rc so far).

2) Back out all ext4 changes that were merged for 2.6.37-rc
   - though Heinz is using XFS exclussively and still reported
     corruption

3) A full git bisect of good=v2.6.36 bad=v2.6.37-rc4 would be the most
   interesting.  Albeit much more tedious.

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