public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org, chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: [PATCH 0/6] nfsd: add support for NFSv4 callbacks over IPv6 (try #5)
Date: Fri, 14 Aug 2009 12:57:53 -0400	[thread overview]
Message-ID: <1250269079-14629-1-git-send-email-jlayton@redhat.com> (raw)

Fifth attempt at a patchset to add support for NFSv4 callbacks over
IPv6. Changes from last patchset are mostly to address Chuck's comments:

1) made the new address comparison and copy routines into static inlines
and added them to clnt.h. Ditto for the get_scope_id function.

2) combined the patch to change nfs4_cb_conn to hold address in
sockaddr_storage with the one to convert gen_callback to use
rpc_uaddr2sockaddr. That eliminates changes to the parse_ipv4 function
that eventually gets ripped out.

Tested using opensolaris and linux and verifying that delegations could
be properly recalled. I also tested mounts to the server's link-local
address and verified that the callback channel connected correctly.

Jeff Layton (6):
  sunrpc: add routine for comparing addresses
  sunrpc: add common routine for copying address portion of a sockaddr
  nfsd: make nfs4_client->cl_addr a struct sockaddr_storage
  nfsd: convert nfs4_cb_conn struct to hold address in sockaddr_storage
  nfsd: add support for NFSv4 callbacks over IPv6
  nfsd: populate sin6_scope_id on callback address with scopeid from
    rq_addr on SETCLIENTID call

 fs/lockd/clntlock.c         |    2 +-
 fs/lockd/host.c             |    4 +-
 fs/lockd/mon.c              |    2 +-
 fs/lockd/svcsubs.c          |    2 +-
 fs/nfsd/nfs4callback.c      |   11 +---
 fs/nfsd/nfs4state.c         |  133 ++++++++++++++-----------------------------
 include/linux/lockd/lockd.h |   43 --------------
 include/linux/nfsd/state.h  |    6 +-
 include/linux/sunrpc/clnt.h |  113 ++++++++++++++++++++++++++++++++++++
 9 files changed, 166 insertions(+), 150 deletions(-)

_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

             reply	other threads:[~2009-08-14 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 16:57 Jeff Layton [this message]
2009-08-14 16:57 ` [PATCH 1/6] sunrpc: add routine for comparing addresses Jeff Layton
2009-08-14 16:57 ` [PATCH 2/6] sunrpc: add common routine for copying address portion of a sockaddr Jeff Layton
2009-08-14 16:57 ` [PATCH 3/6] nfsd: make nfs4_client->cl_addr a struct sockaddr_storage Jeff Layton
2009-08-14 16:57 ` [PATCH 4/6] nfsd: convert nfs4_cb_conn struct to hold address in sockaddr_storage Jeff Layton
2009-08-14 16:57 ` [PATCH 5/6] nfsd: add support for NFSv4 callbacks over IPv6 Jeff Layton
2009-08-14 16:57 ` [PATCH 6/6] nfsd: populate sin6_scope_id on callback address with scopeid from rq_addr on SETCLIENTID call Jeff Layton
2009-08-14 18:05 ` [PATCH 0/6] nfsd: add support for NFSv4 callbacks over IPv6 (try #5) Chuck Lever
2009-08-21 15:44   ` J. Bruce Fields

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=1250269079-14629-1-git-send-email-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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