| 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
| ||
|
Date: Mon, 22 Jan 2007 22:42:21 +0100 From: Christophe Saout <christophe@...ut.de> To: Andrew Morton <akpm@...l.org> Cc: noah <noah123@...il.com>, linux-kernel@...r.kernel.org, dm-devel@...hat.com Subject: Re: Data corruption with raid5/dm-crypt/lvm/reiserfs on 2.6.19.2 Am Montag, den 22.01.2007, 11:56 -0800 schrieb Andrew Morton: > There has been a long history of similar problems when raid and dm-crypt > are used together. I thought a couple of months ago that we were hot on > the trail of a fix, but I don't think we ever got there. Perhaps > Christophe can comment? No, I think it's exactly this bug. Three month ago someone came up with a very reliable test case and I managed to nail down the bug. Readaheads that were aborted by the raid5 code (or some layer below) were signalled using a cleared BIO_UPTODATE bit, but no error code, and were missed as aborted by dm-crypt (all other layers apparently set the error code in this case, so this only happened with raid5) which could mess up the buffer cache. Anyway, it then turned out this bug was already "accidentally" fixed in 2.6.19 by RedHat in order to play nicely with make_request changes (the stuff to reduce stack usage with stacked block device layers), that's why you probably missed that it got fixed. The fix for pre-2.6.19 kernels went into some 2.6.16.x and 2.6.18.6. - 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/
Powered by blists - more mailing lists