From: Piet Delaney <piet@bluelane.com>
To: dm-devel@redhat.com
Subject: Re: [dm-crypt] Re: [stable][PATCH < 2.6.19] Fix data corruption with dm-crypt over RAID5
Date: Mon, 22 Jan 2007 18:19:15 -0800 [thread overview]
Message-ID: <ep3rb5$qc8$1@sea.gmane.org> (raw)
In-Reply-To: 1169473139.1772.5.camel@leto.intern.saout.de
Christophe Saout wrote:
> Am Mittwoch, den 17.01.2007, 00:44 -0800 schrieb Piet Delaney:
>
>> 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.
>
> Yes, it should apply as well.
I'll assume that also means that applying the patch is reasonable.
In our case we aren't using raid5; how ever we are using raid to mirror
two root partitions. Your explanation to Andrew indicates the problem should
only occur when using raid5. So applying the patch should be only have the
effect of making it now possible to use raid5 with dm-crypt. Since we are
currently running raid with root encryption it feels like it's better to
include your patch.
-piet
next prev parent reply other threads:[~2007-01-23 2:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <456B732F.6080906@lelik.org>
[not found] ` <20061129145208.GQ4409@agk.surrey.redhat.com>
[not found] ` <456F46E3.6030702@lelik.org>
[not found] ` <1164983209.24524.20.camel@leto.intern.saout.de>
[not found] ` <20061201152143.GE4409@agk.surrey.redhat.com>
[not found] ` <45704B95.3020308@lelik.org>
[not found] ` <1165026116.29307.18.camel@leto.intern.saout.de>
2006-12-02 2:27 ` [stable][PATCH < 2.6.19] Fix data corruption with dm-crypt over RAID5 Christophe Saout
2006-12-02 3:49 ` Chris Wright
2006-12-02 11:00 ` Christophe Saout
[not found] ` <1165026476.29307.23.camel-EBVayWzc4uH0B753RsUbJiEWGD4kr0XT@public.gmane.org>
2007-01-17 8:44 ` [dm-devel] " Piet Delaney
2007-01-17 8:44 ` Piet Delaney
2007-01-22 13:38 ` [dm-crypt] " Christophe Saout
2007-01-23 2:19 ` Piet Delaney
2007-01-23 2:19 ` Piet Delaney [this message]
2007-02-23 2:49 ` Piet Delaney
2006-12-02 2:27 ` Christophe Saout
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ep3rb5$qc8$1@sea.gmane.org' \
--to=piet@bluelane.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.