From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>
Subject: Re: NFSd in container - it works
Date: Thu, 29 Nov 2012 17:04:02 +0400 [thread overview]
Message-ID: <50B75D42.4030802@parallels.com> (raw)
In-Reply-To: <20121129075508.6f6f1c76@tlielax.poochiereds.net>
29.11.2012 16:55, Jeff Layton пишет:
>
> nfsdcld is being ripped out in 3.10. The binaries for it are already
> gone from nfs-utils. If you disable the legacy and usermode helper
> trackers, then you have nothing left. :)
>
I was going to disable only usermode helper in container for a while (it looks like we have at least half a year till 3.10 kernel).
> I think you'll need to come up with some mechanism to ensure that these
> things are done in the correct container. What that is, and how that
> should work, I'm not sure...
>
This doesn't look that complicated: root have to be taken from task, which starts tracker and stored with NFSd per-net data.
Then it can be passed to usermode helper. And of course, this path have to be grabbed (path_get() must be called).
Not a great design. But it will work, I believe. And doesn't need any changes to other parts of kernel tree...
--
Best regards,
Stanislav Kinsbursky
next prev parent reply other threads:[~2012-11-29 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 17:13 NFSd in container - it works Stanislav Kinsbursky
2012-11-28 20:01 ` bfields
2012-11-28 20:28 ` Jeff Layton
2012-11-29 11:53 ` Stanislav Kinsbursky
2012-11-29 12:13 ` Jeff Layton
2012-11-29 12:48 ` Stanislav Kinsbursky
2012-11-29 12:55 ` Jeff Layton
2012-11-29 13:04 ` Stanislav Kinsbursky [this message]
2012-11-29 14:11 ` Stanislav Kinsbursky
2012-11-29 11:34 ` 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=50B75D42.4030802@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.