From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, bharrosh@panasas.com,
steved@redhat.com, skinsbursky@parallels.com
Subject: [PATCH 0/2] nfsd: add a usermodehelper upcall for client id tracking
Date: Mon, 1 Oct 2012 07:51:36 -0400 [thread overview]
Message-ID: <1349092298-23872-1-git-send-email-jlayton@redhat.com> (raw)
A few months ago I did some patches to add an upcall to replace the
legacy clientid tracking scheme in nfsd. At the time, several people
including Boaz and Steve expressed that they would prefer an upcall that
used call_usermodehelper instead of requiring a running daemon.
While I'm loath to add yet another upcall to the kernel, I must admit
that they have a good point. Yet another running daemon for something as
infrequently called as this is less than ideal. The idiot-proofness of a
usermodehelper upcall is hard to beat for the "just works" factor.
This patchset adds a new set of client tracking ops to the kernel that
use call_usermodehelper to exec a program in userland to do its bidding.
I'll also be posting a set of nfs-utils patches soon to add the callout
program for this.
This seems to work as expected and is fairly simple. There are a couple
of lingering issues.
- Do we need to switch to a different mount namespace somehow based on
the net namespace? Eventually we want to allow nfsd to run in a
container. At some point we'll need a mechanism to ensure that the
upcall runs within the correct container. Stanislav, I'd appreciate
your input here...
- What about nfsdcld? I don't believe any distros have deployed it yet,
and there aren't a lot of compelling reasons to stick with it if this
patchset seems reasonable. I suggest we plan to deprecate it in a couple
of releases unless there are objections.
Unless anyone sees major problems with this approach, I think these
patches are reasonable for 3.7.
Jeff Layton (2):
nfsd: add a usermodehelper upcall for NFSv4 client ID tracking
nfsd: change algorithm for selecting the client_tracking_ops
fs/nfsd/nfs4recover.c | 174 +++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 164 insertions(+), 10 deletions(-)
--
1.7.11.4
next reply other threads:[~2012-10-01 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 11:51 Jeff Layton [this message]
2012-10-01 11:51 ` [PATCH 1/2] nfsd: add a usermodehelper upcall for NFSv4 client ID tracking Jeff Layton
2012-10-01 11:51 ` [PATCH 2/2] nfsd: change algorithm for selecting the client_tracking_ops Jeff Layton
2012-10-01 14:05 ` [PATCH 0/2] nfsd: add a usermodehelper upcall for client id tracking Stanislav Kinsbursky
2012-10-01 14:12 ` bfields
2012-10-01 14:30 ` Stanislav Kinsbursky
2012-10-01 14:48 ` bfields
2012-10-01 15:47 ` Stanislav Kinsbursky
2012-10-01 14:52 ` Jeff Layton
2012-10-01 15:49 ` 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=1349092298-23872-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.com \
--cc=steved@redhat.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).