summaryrefslogtreecommitdiffstats
path: root/fs/nfs/internal.h
diff options
context:
space:
mode:
authorChuck Lever2008-03-14 19:10:22 +0100
committerTrond Myklebust2008-03-19 23:00:19 +0100
commitf22d6d79fe227245363a8849ea8c85fe6c6598c3 (patch)
tree5496ddd3e912a399e0be9a7116fc1a66d6c79a10 /fs/nfs/internal.h
parentNFS: Fix up data types of fields in nfs_parsed_mount_options (diff)
downloadkernel-qcow2-linux-f22d6d79fe227245363a8849ea8c85fe6c6598c3.tar.gz
kernel-qcow2-linux-f22d6d79fe227245363a8849ea8c85fe6c6598c3.tar.xz
kernel-qcow2-linux-f22d6d79fe227245363a8849ea8c85fe6c6598c3.zip
NFS: Save the value of the "port=" mount option
During a remount based on the mount options displayed in /proc/mounts, we want to preserve the original behavior of the mount request. Let's save the original setting of the "port=" mount option in the mount's nfs_server structure. This allows us to simplify the default behavior of port setting for NFSv4 mounts: by default, NFSv2/3 mounts first try an RPC bind to determine the NFS server's port, unless the user specified the "port=" mount option; Users can force the client to skip the RPC bind by explicitly specifying "port=<value>". NFSv4, by contrast, assumes the NFS server port is 2049 and skips the RPC bind, unless the user specifies "port=". Users can force an RPC bind for NFSv4 by explicitly specifying "port=0". I added a couple of extra comments to clarify this behavior. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Cc: Miklos Szeredi <miklos@szeredi.hu> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs/internal.h')
-rw-r--r--fs/nfs/internal.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/nfs/internal.h b/fs/nfs/internal.h
index e89688a955bf..999ad8ee0645 100644
--- a/fs/nfs/internal.h
+++ b/fs/nfs/internal.h
@@ -56,6 +56,7 @@ struct nfs_parsed_mount_data {
size_t addrlen;
char *hostname;
char *export_path;
+ unsigned short port;
unsigned short protocol;
} nfs_server;