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 19:29:26 +0100 [thread overview]
Message-ID: <4D503A06.3010403@redhat.com> (raw)
In-Reply-To: <20110207174552.GC3457@thunk.org>
On 02/07/2011 06:45 PM, Ted Ts'o wrote:
> On Fri, Feb 04, 2011 at 10:40:47PM +0000, Matt wrote:
>>
>> So that means that the file-corruption which existed until 2.6.37-rc6
>> and got triggered (for me) more easily via "dm crypt: scale to
>> multiple CPUs"
>> is fixed now ?
>
> Well, a patch exists for it that will be merged into 2.6.38.
>
>> That should give ext4 a nice speedup for >=2.6.38 :)
>
> I'm not going to make it be the default for 2.6.38, since it's fairly
> late in the -rc features. People who want it can explicitly enable it
> using the mount option mblk_io_submit, though. (And let me know your
> success stories! :-) I will be enabling it as the default in
> 2.6.39-rc1.
So it was ext4 only bug in ext4_end_bio(),
dm-crypt per-cpu code was just trigger here, right?
Milan
next prev parent reply other threads:[~2011-02-07 18:29 UTC|newest]
Thread overview: 9+ 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 [this message]
2011-02-07 18:44 ` Matt
2011-02-07 20:44 ` Ted Ts'o
2011-02-07 20:51 ` Milan Broz
2011-02-07 18:56 ` Matt
-- strict thread matches above, loose matches on Subject: below --
2011-02-01 17:51 Curt Wohlgemuth
2011-02-03 18:38 ` Ted Ts'o
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=4D503A06.3010403@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;
as well as URLs for NNTP newsgroup(s).