From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, xemul@parallels.com, neilb@suse.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jbottomley@parallels.com, bfields@fieldses.org,
davem@davemloft.net, devel@openvz.org
Subject: [PATCH v2 0/6] SUNRPC: make RPC clients use network-namespace-aware PipeFS routines
Date: Wed, 11 Jan 2012 19:17:52 +0400 [thread overview]
Message-ID: <20120111151051.5891.1830.stgit@localhost6.localdomain6> (raw)
This patch set was created in context of clone of git
branch: git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git.
v2:
1) "over-put" of PipeFS mount point in 1st patch of the series fixed, which
allow allows to bisect the patch set.
2) rebased on tag v3.2
This patch set depends on previous patch sets titled:
1) "SUNRPC: initial part of making pipefs work in net ns"
2) "SUNPRC: cleanup PipeFS for network-namespace-aware users"
This patch set is a first part of reworking SUNPRC PipeFS users.
It makes SUNRPC clients using PipeFS nofitications for directory and GSS pipes
dentries creation. With this patch set RPC clients and GSS auth creations
routines doesn't force SUNRPC PipeFS mount point creation which actually means,
that they now can work without PipeFS dentries.
The following series consists of:
---
Stanislav Kinsbursky (6):
SUNRPC: handle RPC client pipefs dentries by network namespace aware routines
SUNRPC: handle GSS AUTH pipes by network namespace aware routines
SUNRPC: subscribe RPC clients to pipefs notifications
SUNRPC: remove RPC client pipefs dentries after unregister
SUNRPC: remove RPC pipefs mount point manipulations from RPC clients code
SUNRPC: remove RPC PipeFS mount point reference from RPC client
fs/nfs/idmap.c | 4 +
fs/nfsd/nfs4callback.c | 2 -
include/linux/nfs.h | 2 -
include/linux/sunrpc/auth.h | 2 +
include/linux/sunrpc/clnt.h | 2 -
net/sunrpc/auth_gss/auth_gss.c | 101 +++++++++++++++++++++------
net/sunrpc/clnt.c | 150 +++++++++++++++++++++++++++++++---------
net/sunrpc/rpc_pipe.c | 19 +++--
net/sunrpc/sunrpc.h | 2 +
9 files changed, 217 insertions(+), 67 deletions(-)
next reply other threads:[~2012-01-11 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 15:17 Stanislav Kinsbursky [this message]
2012-01-11 15:18 ` [PATCH v2 1/6] SUNRPC: handle RPC client pipefs dentries by network namespace aware routines Stanislav Kinsbursky
2012-01-11 15:18 ` [PATCH v2 2/6] SUNRPC: handle GSS AUTH pipes " Stanislav Kinsbursky
2012-01-11 15:18 ` [PATCH v2 3/6] SUNRPC: subscribe RPC clients to pipefs notifications Stanislav Kinsbursky
2012-01-11 15:18 ` [PATCH v2 4/6] SUNRPC: remove RPC client pipefs dentries after unregister Stanislav Kinsbursky
[not found] ` <20120111151051.5891.1830.stgit-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2012-01-11 15:18 ` [PATCH v2 5/6] SUNRPC: remove RPC pipefs mount point manipulations from RPC clients code Stanislav Kinsbursky
2012-01-11 15:18 ` [PATCH v2 6/6] SUNRPC: remove RPC PipeFS mount point reference from RPC client 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=20120111151051.5891.1830.stgit@localhost6.localdomain6 \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=xemul@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).