From: Frans Pop <elendil@planet.nl>
To: Chris Mason <chris.mason@oracle.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
jack@suse.cz, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: What happened to data=guarded?
Date: Tue, 11 Aug 2009 16:54:36 +0200 [thread overview]
Message-ID: <200908111654.38217.elendil@planet.nl> (raw)
In-Reply-To: <20090811133721.GD29224@think>
On Tuesday 11 August 2009, Chris Mason wrote:
> On Tue, Aug 11, 2009 at 03:35:36PM +0200, Frans Pop wrote:
> > Somewhat unrelated, but what happened to the data=guarded patches
> > Chris Mason proposed back in April?
>
> I missed 2.6.31 but plan on sending for 2.6.32. I promised to send
> along a forward port of the patches a while back, but I finally have
> one in testing here. It should go out shortly.
Good to hear. I've so far stayed with data=ordered as I think I'd prefer
data=guarded over data=writeback. I'll certainly give it a try when it's
available.
Thanks,
FJP
next prev parent reply other threads:[~2009-08-11 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 20:03 [PATCH, RFC] ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED Theodore Ts'o
2009-08-10 20:28 ` Jan Kara
2009-08-10 20:55 ` Ric Wheeler
2009-08-11 3:49 ` Al Boldi
2009-08-11 9:33 ` Jan Kara
2009-08-11 11:41 ` Al Boldi
2009-08-11 13:35 ` What happened to data=guarded? (was: ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED) Frans Pop
2009-08-11 13:37 ` Chris Mason
2009-08-11 14:54 ` Frans Pop [this message]
2009-08-11 15:29 ` What happened to data=guarded? Andi Kleen
2009-08-11 15:34 ` Jan Kara
2009-08-11 18:04 ` Eric Sandeen
2009-08-11 18:57 ` Theodore Tso
2009-08-10 16:42 ` Pavel Machek
2009-08-12 20:37 ` Jan Kara
2009-08-11 19:09 ` Andi Kleen
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=200908111654.38217.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--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).