Re: [PATCH] mount: Set protocol family properly for "udp" and "tcp"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 02/16/2010 05:10 PM, Chuck Lever wrote:
> In nfs_nfs_proto_family(), *family is never set if the legacy
> "udp" or "tcp" mount options are specified.  The result is an error
> message at umount time, for example:
> 
> umount.nfs: DNS resolution failed for
>   2001:5c0:1101:2f00:250:8dff:fe95:5c61: ai_family not supported
> 
> even if mount was built with IPv6 support.
> 
> The man page says that "udp" is a synonym for "proto=udp", and
> likewise for "tcp".  Thus, we don't look at config_default_family
> here, but always use AF_INET explicitly, to be consistent with the
> meaning of proto=.
> 
> Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx>
> Reviewed-by: Jeff Layton <jlayton@xxxxxxxxxx>
> ---
Committed...

steved.
--
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

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux