summaryrefslogtreecommitdiffstats
path: root/fs/nfs/callback.h
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2009-03-18 20:48:06 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2009-03-28 16:02:43 -0400
commitf738f5170367b367e38b2d75a413e7b3c52d46a5 (patch)
tree3552d487e54e8c555e4f7083194d46b6eb95fc66 /fs/nfs/callback.h
parenteb16e907781a9da7f272a3e8284c26bc4e4aeb9d (diff)
downloadop-kernel-dev-f738f5170367b367e38b2d75a413e7b3c52d46a5.zip
op-kernel-dev-f738f5170367b367e38b2d75a413e7b3c52d46a5.tar.gz
NFS: Start PF_INET6 callback listener only if IPv6 support is available
Apparently a lot of people need to disable IPv6 completely on their distributor-built systems, which have CONFIG_IPV6_MODULE enabled at build time. They do this by blacklisting the ipv6.ko module. This causes the creation of the NFSv4 callback service listener to fail if CONFIG_IPV6_MODULE is set, but the module cannot be loaded. Now that the kernel's PF_INET6 RPC listeners are completely separate from PF_INET listeners, we can always start PF_INET. Then the NFS client can try to start a PF_INET6 listener, but it isn't required to be available. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs/callback.h')
-rw-r--r--fs/nfs/callback.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/nfs/callback.h b/fs/nfs/callback.h
index bb25d21..e110e28 100644
--- a/fs/nfs/callback.h
+++ b/fs/nfs/callback.h
@@ -72,5 +72,6 @@ extern void nfs_callback_down(void);
extern unsigned int nfs_callback_set_tcpport;
extern unsigned short nfs_callback_tcpport;
+extern unsigned short nfs_callback_tcpport6;
#endif /* __LINUX_FS_NFS_CALLBACK_H */
OpenPOWER on IntegriCloud