From: "Serge E. Hallyn" <serue@us.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] user namespaces: let user_ns be cloned with fairsched
Date: Fri, 5 Dec 2008 08:44:58 -0600 [thread overview]
Message-ID: <20081205144458.GB10037@us.ibm.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0812052106490.14142@tundra.namei.org>
Quoting James Morris (jmorris@namei.org):
> On Wed, 3 Dec 2008, Serge E. Hallyn wrote:
>
> > (These two patches are in the next-unacked branch of
> > git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/userns-2.6.
> > If they get some ACKs, then I hope to feed this into security-next.
> > After these two, I think we're ready to tackle userns+capabilities)
>
> These look ok to me, but no acks so far. Any reason not to apply them?
Thanks for taking a look, James. Yes, there were specific acks I
was looking for.
Dhaval, could you take a look at the first one and tell me if it
is a problem for fairsched?
Eric, could you take a look at the second one? Actually, Daniel,
you've played with file capabilities for liblxc - would
http://lkml.org/lkml/2008/12/3/277 be a problem for you?
thanks,
-serge
next prev parent reply other threads:[~2008-12-05 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 19:17 [PATCH 1/2] user namespaces: let user_ns be cloned with fairsched Serge E. Hallyn
2008-12-03 19:17 ` [PATCH 2/2] user namespaces: require cap_set{ug}id for CLONE_NEWUSER Serge E. Hallyn
2008-12-05 16:24 ` Eric W. Biederman
2008-12-05 16:45 ` Serge E. Hallyn
2008-12-05 17:17 ` Eric W. Biederman
2008-12-05 17:14 ` Eric W. Biederman
2008-12-07 22:47 ` James Morris
2008-12-05 10:07 ` [PATCH 1/2] user namespaces: let user_ns be cloned with fairsched James Morris
2008-12-05 14:44 ` Serge E. Hallyn [this message]
2008-12-07 22:46 ` James Morris
2008-12-08 16:04 ` Serge E. Hallyn
2008-12-08 21:15 ` James Morris
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=20081205144458.GB10037@us.ibm.com \
--to=serue@us.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.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