From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, chuck.lever@oracle.com
Subject: Re: [PATCH 0/4] nfsd: add support for NFSv4 callbacks over IPv6
Date: Wed, 17 Jun 2009 14:47:01 -0400 [thread overview]
Message-ID: <20090617184701.GD24040@fieldses.org> (raw)
In-Reply-To: <1245262541-9362-1-git-send-email-jlayton@redhat.com>
On Wed, Jun 17, 2009 at 02:15:37PM -0400, Jeff Layton wrote:
> This patchset is a first pass at adding IPv6 callback channel support
> for knfsd. The set is fairly straightforward, but it does require a
> number of changes to server side NFSv4 related structs that store
> addresses in places that are only suitable for IPv4 addresses.
>
> I've tested this by having Linux and OpenSolaris clients mount the
> server over an IPv6 socket, get a delegation and ensure that the server
> can recall that delegation. It all seems to work as expected. IPv4
> callbacks also seem to continue to work correctly.
>
> This patchset does change the some of the new 4.1 functions
> (nfsd4_exchange_id in particular). Those changes are untested as of yet
> but I'll see if I can do so if the approach in this set seems
> reasonable.
Thanks, just two quick comments:
1. I've been working on the callback code, so check that this
applies against for-2.6.31 (at
git://linux-nfs.org/~bfields/linux.git).
2. Any IP address checks in setclientid or exchange_id are
probably bogus; the former should be gone, the latter may still
be there but there'll be a patch queued up for 2.6.31 to fix
that.
--b.
>
> Comments welcome...
>
> Jeff Layton (4):
> nfsd: convert nfs4_callback struct to hold address in
> sockaddr_storage
> nfsd: break out setclientid port parsing into separate routine
> nfsd: make nfs4_client->cl_addr a struct sockaddr_storage
> nfsd: add support for NFSv4 callbacks over IPv6
>
> fs/nfsd/nfs4callback.c | 11 +--
> fs/nfsd/nfs4state.c | 220 ++++++++++++++++++++++++++++++++++++-------
> include/linux/nfsd/state.h | 6 +-
> 3 files changed, 189 insertions(+), 48 deletions(-)
>
next prev parent reply other threads:[~2009-06-17 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 18:15 [PATCH 0/4] nfsd: add support for NFSv4 callbacks over IPv6 Jeff Layton
2009-06-17 18:15 ` [PATCH 1/4] nfsd: convert nfs4_callback struct to hold address in sockaddr_storage Jeff Layton
2009-06-17 18:15 ` [PATCH 2/4] nfsd: break out setclientid port parsing into separate routine Jeff Layton
2009-06-17 18:15 ` [PATCH 3/4] nfsd: make nfs4_client->cl_addr a struct sockaddr_storage Jeff Layton
2009-06-17 18:15 ` [PATCH 4/4] nfsd: add support for NFSv4 callbacks over IPv6 Jeff Layton
2009-06-17 18:47 ` J. Bruce Fields [this message]
2009-06-17 19:01 ` [PATCH 0/4] " Jeff Layton
[not found] <76bd70e30906171223r1f286d0eg1e64510f106d3027@mail.gmail.com>
[not found] ` <76bd70e30906171223r1f286d0eg1e64510f106d3027-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-17 20:55 ` Jeff Layton
[not found] ` <76bd70e30906171432m29b3f179y6d0f2111e205114c@mail.gmail.com>
[not found] ` <76bd70e30906171432m29b3f179y6d0f2111e205114c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-18 1:06 ` Jeff Layton
[not found] ` <20090617210623.4c7860fb-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-18 4:28 ` Chuck Lever
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=20090617184701.GD24040@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox