From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ian Kent <ikent@redhat.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Oleg Nesterov <onestero@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Benjamin Coddington <bcodding@redhat.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
Jeff Layton <jeff.layton@primarydata.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC PATCH 0/5] Second attempt at contained helper execution
Date: Wed, 14 Jan 2015 17:10:11 -0500 [thread overview]
Message-ID: <20150114221011.GC7071@fieldses.org> (raw)
In-Reply-To: <20150114215525.GB7071@fieldses.org>
> On Wed, Jan 14, 2015 at 05:32:22PM +0800, Ian Kent wrote:
> > There are other difficulties to tackle as well, such as how to decide
> > if contained helper execution is needed. For example, if a mount has
> > been propagated to a container or bound into the container tree (such
> > as with the --volume option of "docker run") the root init namespace
> > may need to be used and not the container namespace.
I think you have to go through each of the existing upcall examples and
decide what's needed for each.
At least for the nfsv4 idmapper I would've thought the namespace the
mount was done in would be the right choice, hence my previous question.
--b.
next prev parent reply other threads:[~2015-01-14 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 9:32 [RFC PATCH 0/5] Second attempt at contained helper execution Ian Kent
2015-01-14 9:32 ` [RFC PATCH 1/5] nsproxy - refactor setns() Ian Kent
2015-01-14 9:32 ` [RFC PATCH 2/5] kmod - rename call_usermodehelper() flags parameter Ian Kent
2015-01-14 9:32 ` [RFC PATCH 3/5] kmod - teach call_usermodehelper() to use a namespace Ian Kent
2015-01-15 16:45 ` Jeff Layton
2015-01-16 1:18 ` Ian Kent
2015-01-14 9:32 ` [RFC PATCH 4/5] KEYS - rename call_usermodehelper_keys() flags parameter Ian Kent
2015-01-14 9:32 ` [RFC PATCH 5/5] KEYS: exec request-key within the requesting task's init namespace Ian Kent
2015-01-14 21:55 ` [RFC PATCH 0/5] Second attempt at contained helper execution J. Bruce Fields
2015-01-14 22:10 ` J. Bruce Fields [this message]
2015-01-15 0:26 ` Ian Kent
2015-01-15 16:27 ` J. Bruce Fields
2015-01-16 1:01 ` Ian Kent
2015-01-16 15:25 ` J. Bruce Fields
2015-01-21 7:05 ` Ian Kent
2015-01-21 14:38 ` J. Bruce Fields
2015-01-22 1:28 ` Ian Kent
2015-02-18 20:44 ` J. Bruce Fields
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=20150114221011.GC7071@fieldses.org \
--to=bfields@fieldses.org \
--cc=bcodding@redhat.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=ikent@redhat.com \
--cc=jeff.layton@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=onestero@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=viro@ZenIV.linux.org.uk \
/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