linux-kernel - Re: [dm-devel] 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20101205202855.GA7668@basil.fritz.box>
Date:	Sun, 5 Dec 2010 21:28:55 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Theodore Tso <tytso@....EDU>
Cc:	device-mapper development <dm-devel@...hat.com>,
	Heinz Diehl <htd@...tha.org>, Jon Nelson <jnelson@...poni.net>,
	htejun@...il.com, Matt <jackdachef@...il.com>,
	Mike Snitzer <snitzer@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.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: [dm-devel] hunt for 2.6.37 dm-crypt+ext4 corruption?

> I've been using a kernel which is between 2.6.37-rc2 and -rc3 with a LUKS / dm-crypt / LVM / ext4 setup for my primary file systems, and I haven't observed any corruption for the last two weeks or so.   It's on my todo list to upgrade to top of Linus's tree, but perhaps this is a useful data point.

The reported corruptions are with a .37 forward port someone did of my parallel 
kcryptd patch.  The 2.6.36 (and earlier) versions are rock solid with many users.

The classic dmcrypt is single threaded and very slow.

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

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/