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/4] SUNRPC: service release in network namespace context
Date: Tue, 31 Jan 2012 14:08:50 +0400 [thread overview]
Message-ID: <20120131100625.4342.34539.stgit@localhost6.localdomain6> (raw)
v2: Added comment to BUG_ON's in svc_destroy() to make code looks clearer.
This patch set is the final step towards to making LockD network namespace
aware.
I can't prove, that this patch set is enough for NFSd (just haven't try), by
Lockd works fine and patches for it will be send soon.
The following series consists of:
---
Stanislav Kinsbursky (4):
SUNRPC: clear svc pools lists helper introduced
SUNRPC: clear svc transports lists helper introduced
SUNRPC: service destruction in network namespace context
SUNRPC: service shutdown function in network namespace context introduced
include/linux/sunrpc/svcsock.h | 2 +-
net/sunrpc/svc.c | 38 ++++++++++++++++++++++++----------
net/sunrpc/svc_xprt.c | 45 ++++++++++++++++++++++++++++------------
3 files changed, 59 insertions(+), 26 deletions(-)
next reply other threads:[~2012-01-31 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 10:08 Stanislav Kinsbursky [this message]
2012-01-31 10:09 ` [PATCH v2 1/4] SUNRPC: clear svc pools lists helper introduced Stanislav Kinsbursky
2012-01-31 10:09 ` [PATCH v2 2/4] SUNRPC: clear svc transports " Stanislav Kinsbursky
2012-01-31 10:09 ` [PATCH v2 3/4] SUNRPC: service destruction in network namespace context Stanislav Kinsbursky
2012-01-31 10:09 ` [PATCH v2 4/4] SUNRPC: service shutdown function in network namespace context introduced 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=20120131100625.4342.34539.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).