From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Serge Hallyn" <serue@us.ibm.com>,
"Subrata Modak" <subrata@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org, clg@fr.ibm.com, herbert@13thfloor.at,
dev@sw.ru
Subject: Re: Current state of CLONE_NEWUSER?
Date: Thu, 20 Nov 2008 06:49:54 -0500 [thread overview]
Message-ID: <cfd18e0f0811200349q788c2767i5164dc1c47e67925@mail.gmail.com> (raw)
In-Reply-To: <m1vdujdvi6.fsf@frodo.ebiederm.org>
Hi Eric,
On Wed, Nov 19, 2008 at 8:41 PM, Eric W. Biederman
<ebiederm@xmission.com> wrote:
> "Michael Kerrisk" <mtk.manpages@googlemail.com> writes:
>
>> Hi Serge,
>>
>> What is the current status of CLONE_NEWUSER? I'm currently trying to
>> test this flag in preparation for documenting it in the clone(2) man
>> page, but am running into an ENOMEM error from the clone() call, which
>> seems to occur after a failure in kobject_init_and_add() in the
>> following call sequence:
>>
>> clone_user_ns() --> alloc_uid() --> uids_user_create() -->
>> kobject_init_and_add()
>>
>> Are there already some test programs somewhere? Is there any
>> documentation already available for this flag?
>
> This code is definitely still under development.
>
> When complete it should be able to create a new uid namespace,
> as an unprivileged user. Creating a new process with uid == gid == 0.
> Have a full set of caps. And have permission to do nothing on the system
> except read world readable files and write world writable files.
Thanks for the info,
So the error I described is expected?
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-11-20 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 20:04 Michael Kerrisk
2008-11-20 1:41 ` Eric W. Biederman
2008-11-20 11:49 ` Michael Kerrisk [this message]
2008-11-20 17:33 ` Eric W. Biederman
2008-11-21 15:07 ` Serge E. Hallyn
2008-11-25 15:54 ` Michael Kerrisk
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=cfd18e0f0811200349q788c2767i5164dc1c47e67925@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=serue@us.ibm.com \
--cc=subrata@linux.vnet.ibm.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
all inboxes | Powered by JetHome®