NFS: Allow text-based mounts via compat_sys_mount
authorChuck Lever <chuck.lever@oracle.com>
Wed, 13 Feb 2008 19:55:17 +0000 (14:55 -0500)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Thu, 14 Feb 2008 04:24:05 +0000 (23:24 -0500)
commit4267c9561d9c3bb2abf45abed9c75a1c892d7d15
treecc2d15122ac06bebb25c87b53dc61e387c70f350
parent8e60029f403781b8a63b7ffdb7dc1faff6ca651e
NFS: Allow text-based mounts via compat_sys_mount

The compat_sys_mount() system call throws EINVAL for text-based NFSv4
mounts.

The text-based mount interface assumes that any mount option blob that
doesn't set the version field to "1" is a C string (ie not a legacy
mount request).  The compat_sys_mount() call treats blobs that don't
set the version field to "1" as an error.  We just relax the check in
compat_sys_mount() a bit to allow C strings to be passed down to the NFSv4
client.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/compat.c