NFSv4: Fix the 'nolock' option regression
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Wed, 17 Jun 2009 20:22:58 +0000 (13:22 -0700)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Wed, 17 Jun 2009 20:22:58 +0000 (13:22 -0700)
NFSv4 should just ignore the 'nolock' option. It is an NFSv2/v3 thing...
This fixes the Oops in http://bugzilla.kernel.org/show_bug.cgi?id=13330

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/super.c

index 26127b69a2755c66e3713a119259051f018745bc..98b47d17740ade7c182a1ea3bd75f57362253625 100644 (file)
@@ -2240,6 +2240,11 @@ static void nfs4_fill_super(struct super_block *sb)
        nfs_initialise_sb(sb);
 }
 
+static void nfs4_validate_mount_flags(struct nfs_parsed_mount_data *args)
+{
+       args->flags &= ~(NFS_MOUNT_NONLM|NFS_MOUNT_NOACL|NFS_MOUNT_VER3);
+}
+
 /*
  * Validate NFSv4 mount options
  */
@@ -2336,6 +2341,8 @@ static int nfs4_validate_mount_data(void *options,
 
                nfs_validate_transport_protocol(args);
 
+               nfs4_validate_mount_flags(args);
+
                if (args->auth_flavor_len > 1)
                        goto out_inval_auth;