public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: [PATCH 0/4] nfsd: add support for NFSv4 callbacks over IPv6 (try #3)
Date: Mon, 10 Aug 2009 18:09:13 -0400	[thread overview]
Message-ID: <1249942157-12613-1-git-send-email-jlayton@redhat.com> (raw)

Third attempt at a patchset to add support for NFSv4 callbacks over
IPv6. The main change here is that this set uses the standard routines
for address conversion that were recently added to the RPC layer in
Bruce's tree. Not only does this add IPv6 support but it's a net code
reduction.

There are also some other minor cleanups. The set should apply cleanly
to Bruce's tree as of earlier today.

Tested using opensolaris and linux clients and watching the traffic with
wireshark.

Jeff Layton (4):
  nfsd: convert nfs4_cb_conn struct to hold address in sockaddr_storage
  nfsd: make nfs4_client->cl_addr a struct sockaddr_storage
  nfsd: convert gen_callback to use rpc_uaddr2sockaddr
  nfsd: add support for NFSv4 callbacks over IPv6

 fs/nfsd/nfs4callback.c     |   11 +--
 fs/nfsd/nfs4state.c        |  176 ++++++++++++++++++++++----------------------
 include/linux/nfsd/state.h |    6 +-
 3 files changed, 93 insertions(+), 100 deletions(-)


             reply	other threads:[~2009-08-10 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 22:09 Jeff Layton [this message]
2009-08-10 22:09 ` [PATCH 1/4] nfsd: convert nfs4_cb_conn struct to hold address in sockaddr_storage Jeff Layton
2009-08-10 22:09 ` [PATCH 2/4] nfsd: make nfs4_client->cl_addr a struct sockaddr_storage Jeff Layton
2009-08-10 22:53   ` Chuck Lever
2009-08-11 11:02     ` Jeff Layton
2009-08-10 22:09 ` [PATCH 3/4] nfsd: convert gen_callback to use rpc_uaddr2sockaddr Jeff Layton
2009-08-10 22:09 ` [PATCH 4/4] nfsd: add support for NFSv4 callbacks over IPv6 Jeff Layton

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=1249942157-12613-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