From: Jan Kara <jack@suse.cz>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] ext3: make barrier options consistent with ext4
Date: Mon, 3 May 2010 18:36:09 +0200 [thread overview]
Message-ID: <20100503163609.GD3470@quack.suse.cz> (raw)
In-Reply-To: <4BDB00BE.7040600@redhat.com>
On Fri 30-04-10 11:09:34, Eric Sandeen wrote:
> ext4 was updated to accept barrier/nobarrier mount options
> in addition to the older barrier=0/1. The barrier story
> is complex enough, we should help people by making the options
> the same at least, even if the defaults are different.
>
> This patch allows the barrier/nobarrier mount options for ext3,
> while keeping nobarrier the default.
>
> It also unconditionally displays barrier status in show_options,
> and prints a message at mount time if barriers are not enabled,
> just as ext4 does.
Thanks. Added to my tree.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-05-03 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 16:09 [PATCH] ext3: make barrier options consistent with ext4 Eric Sandeen
2010-05-03 16:36 ` Jan Kara [this message]
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=20100503163609.GD3470@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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 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).