From: Eric Sandeen <sandeen@redhat.com>
To: Josh Boyer <jwboyer@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, kernel-team@fedoraproject.org
Subject: Re: [PATCH] ext4: Support "check=none" "nocheck" mount options
Date: Tue, 10 Jan 2012 11:43:41 -0600 [thread overview]
Message-ID: <4F0C78CD.6070809@redhat.com> (raw)
In-Reply-To: <20120110174118.GB3015@zod.bos.redhat.com>
On 1/10/12 11:41 AM, Josh Boyer wrote:
> The ext2/ext3 filesystems supported "check=none" and "nocheck" as mount options
> even though that was already the default behavior and it essentially did
> nothing. When using ext4 to mount ext2/ext3 filesystems, that mount option
> causes the mount to fail. That isn't as backward compatible as it could be,
> so add support to ext4 to accept the option.
The only thing ext2 does with those options today is to clear the flag,
and I can't find anything in userspace or kernelspace which would have set
it in any case. It seem dead, but we do need the compatibility in ext4
if it's to handle ext2&3 seamlessly, I guess.
> Signed-off-by: Josh Boyer <jwboyer@redhat.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
>
> ---
> fs/ext4/super.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 3e1329e..5ff09e7 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -1333,7 +1333,7 @@ enum {
> Opt_nomblk_io_submit, Opt_block_validity, Opt_noblock_validity,
> Opt_inode_readahead_blks, Opt_journal_ioprio,
> Opt_dioread_nolock, Opt_dioread_lock,
> - Opt_discard, Opt_nodiscard, Opt_init_itable, Opt_noinit_itable,
> + Opt_discard, Opt_nodiscard, Opt_init_itable, Opt_noinit_itable, Opt_nocheck,
> };
>
> static const match_table_t tokens = {
> @@ -1409,6 +1409,8 @@ static const match_table_t tokens = {
> {Opt_init_itable, "init_itable=%u"},
> {Opt_init_itable, "init_itable"},
> {Opt_noinit_itable, "noinit_itable"},
> + {Opt_nocheck, "check=none"},
> + {Opt_nocheck, "nocheck"},
> {Opt_err, NULL},
> };
>
> @@ -1905,6 +1907,9 @@ set_qf_format:
> case Opt_noinit_itable:
> clear_opt(sb, INIT_INODE_TABLE);
> break;
> + case Opt_nocheck:
> + /* ext2/ext3 used to "support" this option. Silently eat it */
> + break;
> default:
> ext4_msg(sb, KERN_ERR,
> "Unrecognized mount option \"%s\" "
next prev parent reply other threads:[~2012-01-10 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 17:41 [PATCH] ext4: Support "check=none" "nocheck" mount options Josh Boyer
2012-01-10 17:43 ` Eric Sandeen [this message]
2012-01-11 10:07 ` Andreas Dilger
2012-01-11 14:50 ` Josh Boyer
2012-01-11 21:07 ` Andreas Dilger
2012-01-11 15:13 ` Eric Sandeen
2012-01-11 15:26 ` Ted Ts'o
2012-01-11 15:35 ` Eric Sandeen
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=4F0C78CD.6070809@redhat.com \
--to=sandeen@redhat.com \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-ext4@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).