Commit 1f3fae1fb25168aac187ff1881738c8ad53a8763 made mount.nfs start looking up and trying to use IPv6 addresses when mount.nfs was built against libtirpc (even when --enable-ipv6 wasn't specified). The problem seems to be that nfs_nfs_proto_family() is basing the family on HAVE_LIBTIRPC. I think it should be basing it on IPV6_SUPPORTED instead. Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> Acked-by: Chuck Lever <chuck.lever@xxxxxxxxxx> --- utils/mount/network.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/utils/mount/network.c b/utils/mount/network.c index e3ad5c2..906e20c 100644 --- a/utils/mount/network.c +++ b/utils/mount/network.c @@ -1344,7 +1344,7 @@ int nfs_nfs_proto_family(struct mount_options *options, unsigned long protocol; char *option; -#ifdef HAVE_LIBTIRPC +#ifdef IPV6_SUPPORTED *family = AF_UNSPEC; #else *family = AF_INET; -- 1.6.5.2 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
