From: Milan Broz <mbroz@redhat.com>
To: "Ted Ts'o" <tytso@mit.edu>, Matt <jackdachef@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: ext4: Fix data corruption with multi-block writepages support
Date: Mon, 07 Feb 2011 21:51:38 +0100 [thread overview]
Message-ID: <4D505B5A.1000203@redhat.com> (raw)
In-Reply-To: <20110207204419.GE3457@thunk.org>
On 02/07/2011 09:44 PM, Ted Ts'o wrote:
> So the fact that we found and fixed an ext4 bug that was triggered by
> dm_crypt should not be taken as a statement (one way or the other)
> that dm_crypt is Bug-Free(tm). :-)
Really? Sigh. ;-)
(There is a rule that if dm-crypt+XFS bug appears, the problem
is always in dm-crypt. So I am quite surprised that this time there
was NO bug in dm-crypt... yet :-)
Anyway, I would like to know if still some problem remains...
Thanks,
Milan
next prev parent reply other threads:[~2011-02-07 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:40 ext4: Fix data corruption with multi-block writepages support Matt
2011-02-07 17:45 ` Ted Ts'o
2011-02-07 18:29 ` Milan Broz
2011-02-07 18:44 ` Matt
2011-02-07 20:44 ` Ted Ts'o
2011-02-07 20:51 ` Milan Broz [this message]
2011-02-07 18:56 ` Matt
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=4D505B5A.1000203@redhat.com \
--to=mbroz@redhat.com \
--cc=jackdachef@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox