linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, skinsbursky@parallels.com
Subject: [PATCH v7 0/5] nfsd: overhaul the client name tracking code
Date: Wed, 29 Feb 2012 12:15:52 -0500	[thread overview]
Message-ID: <1330535757-24925-1-git-send-email-jlayton@redhat.com> (raw)

This is the seventh iteration of this patchset. The primary motivation
for the respin here is to deal with the changes introduced by Stanislav's
"namespacification" of rpc_pipefs.

My conversion here is fairly simple-minded. Since most of the existing
nfsd code works under the aegis of "init_net", this patchset makes the
new code do basically the same thing.

I've not done any real work to make this do different pipes for different
namespaces or anything. As a result, the initialization of the client
tracking will currently fail if rpc_pipefs isn't mounted.

Comments or suggestions on this are welcome. I'm still trying to wrap
my brain around how all of this namespace stuff is supposed to work,
so it's quite possible I've overlooked something. In particular, I'd
like Stanislav's feedback since he's done the bulk of the rpc_pipefs
namespace work so far.

An earlier version of this patchset can be viewed here. That set also
contains a more comprehensive description of the rationale for doing
this:

    http://www.spinics.net/lists/linux-nfs/msg26324.html

Jeff Layton (5):
  nfsd: add nfsd4_client_tracking_ops struct and a way to set it
  sunrpc: create nfsd dir in rpc_pipefs
  nfsd: convert nfs4_client->cl_cb_flags to a generic flags field
  nfsd: add a header describing upcall to nfsdcld
  nfsd: add the infrastructure to handle the cld upcall

 fs/nfsd/nfs4callback.c   |   14 +-
 fs/nfsd/nfs4proc.c       |    3 +-
 fs/nfsd/nfs4recover.c    |  515 ++++++++++++++++++++++++++++++++++++++++++++--
 fs/nfsd/nfs4state.c      |   50 ++---
 fs/nfsd/state.h          |   24 ++-
 include/linux/nfsd/cld.h |   56 +++++
 net/sunrpc/rpc_pipe.c    |    5 +
 7 files changed, 604 insertions(+), 63 deletions(-)
 create mode 100644 include/linux/nfsd/cld.h

-- 
1.7.7.6


             reply	other threads:[~2012-02-29 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 17:15 Jeff Layton [this message]
2012-02-29 17:15 ` [PATCH v7 1/5] nfsd: add nfsd4_client_tracking_ops struct and a way to set it Jeff Layton
2012-02-29 17:15 ` [PATCH v7 2/5] sunrpc: create nfsd dir in rpc_pipefs Jeff Layton
2012-02-29 17:15 ` [PATCH v7 3/5] nfsd: convert nfs4_client->cl_cb_flags to a generic flags field Jeff Layton
2012-02-29 17:15 ` [PATCH v7 4/5] nfsd: add a header describing upcall to nfsdcld Jeff Layton
2012-02-29 17:15 ` [PATCH v7 5/5] nfsd: add the infrastructure to handle the cld upcall Jeff Layton
2012-02-29 18:39   ` Stanislav Kinsbursky
2012-02-29 19:45     ` Jeff Layton
2012-02-29 21:44       ` bfields
2012-03-01  7:31         ` Stanislav Kinsbursky
2012-03-01  7:29       ` Stanislav Kinsbursky

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=1330535757-24925-1-git-send-email-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@parallels.com \
    /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;
as well as URLs for NNTP newsgroup(s).