Christophe Saout wrote:
> Fix corruption issue with dm-crypt on top of software raid5. Cancelled
> readahead bio's that report no error, just have BIO_UPTODATE cleared
> were reported as successful reads to the higher layers (and leaving
> random content in the buffer cache). Already fixed in 2.6.
On Sat, 2006-12-02 at 03:27 +0100, Christophe Saout wrote:
Hi Christophe:
I'm wondering about trying out your patch with dm-crypt on 2.6.12.
The code in drivers/md/dm-crypt.c`crypt_endio() appears to be the same.
Is there a reason that this isn't necessary or would be a bad idea.
Looks like the
Am Freitag, den 01.12.2006, 19:49 -0800 schrieb Chris Wright:
> * Christophe Saout ([EMAIL PROTECTED]) wrote:
> > Fix corruption issue with dm-crypt on top of software raid5. Cancelled
> > readahead bio's that report no error, just have BIO_UPTODATE cleared
> > were reported as successful reads to
[Note: please Cc: [EMAIL PROTECTED] on -stable patches]
* Christophe Saout ([EMAIL PROTECTED]) wrote:
> Fix corruption issue with dm-crypt on top of software raid5. Cancelled
> readahead bio's that report no error, just have BIO_UPTODATE cleared
> were reported as successful reads to the higher la
Fix corruption issue with dm-crypt on top of software raid5. Cancelled
readahead bio's that report no error, just have BIO_UPTODATE cleared
were reported as successful reads to the higher layers (and leaving
random content in the buffer cache). Already fixed in 2.6.19.
Signed-off-by: Christophe Sa
5 matches
Mail list logo