[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080518210625.13450.71349.stgit@ellison.1015granger.net>
Date: Sun, 18 May 2008 17:19:55 -0400
From: Chuck Lever <chuck.lever@...cle.com>
To: netdev@...r.kernel.org
Subject: [PATCH 0/4] RFC: raw IPv6 address parsing in NFS client
Hi-
I'm interested in some review of the following four patches which add to
the kernel's NFS client the ability to parse IPv6 addresses in presentation
format.
Namely, it adds the following:
1. If the user passes in an IPv6 address as the server name, the colons
in the address will confuse the logic that splits the device name
into a server hostname and an export path. We'll use square brackets
around IPv6 server addresses to "escape" the colons, as does Solaris.
2. If the user passes in a link-local IPv6 address as the server name,
an interface index is also necessary. We'll use the "%id" suffix on
the address to pass in the index, and plant that in the sockaddr's
sin6_scope_id field.
In addition to the following patches in email, a git repo with these
same patches already applied can be found here:
linux-nfs.org:exports/cel-2.6.git
The basic questions:
Are these reasonable conventions to follow? Is the parsing logic adequate?
Is there anything I'm forgetting?
Thanks for any review.
---
Chuck Lever (4):
NFS: handle interface identifiers in incoming IPv6 addresses
NFS: Add string length argument to nfs_parse_server_address
NFS: Support raw IPv6 address hostnames during NFS mount operation
NFS: Use common device name parsing logic for NFSv4 and NFSv2/v3
fs/nfs/super.c | 311 ++++++++++++++++++++++++++++++++++++++++++--------------
1 files changed, 236 insertions(+), 75 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists