On May 20, 2008, at 3:32 PM, Trond Myklebust wrote:
On Tue, 2008-05-20 at 12:54 -0400, Chuck Lever wrote:
So, I haven't added IPv6 support in this area because it seems to
assume an IPv4 address here, and it needs to handle the case where
this might be a hostname (ie there should be a DNS resolution in this
path).
If you're going to call in4_pton(), it really should call
nfs_parse_server_address() instead; then this path would magically
support IPv6 addresses as well.
But in the long run, this path will need either an upcall or it will
have to use the key-based kernel DNS resolution facility (Jeff Layton
mentioned something like this over lunch last week).
No. The correct way to do this is to replace the current code
fs_locations handler so that we do the mount from userspace. In
addition
to voiding the whole issue of in-kernel DNS resolution, that also has
the benefit that it allows us to put policy decisions like which
server
to mount from under administrator control in userspace.
I've already started coding up a solution.
Okay, I remembered incorrectly.
I assume this new mechanism is intended to handle IPv6 addresses and
DNS resolution correctly because it will invoke mount.nfs.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
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
