From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] NFS mounting with raw IPv6 server hostnames
Date: Tue, 17 Jun 2008 20:07:24 -0400 [thread overview]
Message-ID: <1213747644.7288.98.camel@localhost> (raw)
In-Reply-To: <20080617181622.3215.61295.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
On Tue, 2008-06-17 at 14:17 -0400, Chuck Lever wrote:
> Hi Trond-
>
> Something meatier today.
>
> These four patches introduce the ability to mount NFS servers using a raw
> IPv6 address. This support requires the ability to handle colons in the
> passed-in server hostname, and the ability to handle an IPv6 interface
> identifier in the passed-in server hostname.
>
> IPv6 addresses contain colons. A colon is also used to separate the server
> name from the export path. By enclosing an IPv6 address inside square
> brackets we effectively escape the colons in the IPv6 address and allow them
> to pass unrecognized through the device name parser.
>
> As an added bonus, I also include the patch that changes
> nfs_parse_server_address() to take a name length. This allows the passed-in
> address string to have no '\0'-termination, which will help us support IPv6
> for NFSv4 referrals.
>
> Please consider these for 2.6.27.
>
> ---
>
> 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 | 336 ++++++++++++++++++++++++++++++++++++++++++++------------
> 1 files changed, 261 insertions(+), 75 deletions(-)
>
All 4 patches applied to the 'devel' branch.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2008-06-18 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 18:17 [PATCH 0/4] NFS mounting with raw IPv6 server hostnames Chuck Lever
[not found] ` <20080617181622.3215.61295.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-17 18:17 ` [PATCH 1/4] NFS: Use common device name parsing logic for NFSv4 and NFSv2/v3 Chuck Lever
[not found] ` <20080617181719.3215.5824.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-17 20:33 ` Trond Myklebust
2008-06-17 20:37 ` Trond Myklebust
2008-06-17 20:47 ` Chuck Lever
2008-06-17 20:41 ` Chuck Lever
2008-06-17 18:17 ` [PATCH 2/4] NFS: Support raw IPv6 address hostnames during NFS mount operation Chuck Lever
2008-06-17 18:17 ` [PATCH 3/4] NFS: Add string length argument to nfs_parse_server_address Chuck Lever
2008-06-17 18:17 ` [PATCH 4/4] NFS: handle interface identifiers in incoming IPv6 addresses Chuck Lever
2008-06-18 0:07 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213747644.7288.98.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.