From patchwork Tue Jan 10 17:41:19 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Josh Boyer X-Patchwork-Id: 135270 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id DEA3EB6FC9 for ; Wed, 11 Jan 2012 04:41:57 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932779Ab2AJRlY (ORCPT ); Tue, 10 Jan 2012 12:41:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:36887 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932685Ab2AJRlX (ORCPT ); Tue, 10 Jan 2012 12:41:23 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0AHfL6g006352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Jan 2012 12:41:21 -0500 Received: from zod.bos.redhat.com (ovpn-113-137.phx2.redhat.com [10.3.113.137]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q0AHfJiA011768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 10 Jan 2012 12:41:21 -0500 Date: Tue, 10 Jan 2012 12:41:19 -0500 From: Josh Boyer To: "Theodore Ts'o" Cc: linux-ext4@vger.kernel.org, sandeen@redhat.com, kernel-team@fedoraproject.org Subject: [PATCH] ext4: Support "check=none" "nocheck" mount options Message-ID: <20120110174118.GB3015@zod.bos.redhat.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25 Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org 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. Signed-off-by: Josh Boyer Reviewed-by: Eric Sandeen --- 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\" "