NFS: Start PF_INET6 callback listener only if IPv6 support is available
authorChuck Lever <chuck.lever@oracle.com>
Thu, 19 Mar 2009 00:48:06 +0000 (20:48 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Sat, 28 Mar 2009 20:02:43 +0000 (16:02 -0400)
commitf738f5170367b367e38b2d75a413e7b3c52d46a5
tree3552d487e54e8c555e4f7083194d46b6eb95fc66
parenteb16e907781a9da7f272a3e8284c26bc4e4aeb9d
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>
fs/nfs/callback.c
fs/nfs/callback.h
fs/nfs/nfs4state.c