From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: util-linux@vger.kernel.org, "Eric W. Biederman" <ebiederm@xmission.com>
Subject: is one allowed to reenter a user namespace?
Date: Mon, 21 Jan 2013 00:36:22 +0100 [thread overview]
Message-ID: <20130120233621.GI17370@in.waw.pl> (raw)
Hi,
when trying to enter a namespace, the behaviour wrt. to entering an
existing namespace that the process is _already_ a part of is
different for user names and all other namespaces. For user namespaces
one gets EINVAL, while for other namespaces it succeeds. In other
words, for user namespaces only, entering the namspace is not idempotent.
# unshare --mount sleep 10000 &
# nsenter --target=$(pgrep sleep) --mount /bin/true
# nsenter --target=$(pgrep sleep) --ipc /bin/true
# nsenter --target=$(pgrep sleep) --net /bin/true
# nsenter --target=$(pgrep sleep) --uts /bin/true
# nsenter --target=$(pgrep sleep) --user /bin/true
nsenter: setns of 'ns/user' failed: Invalid argument
(and the EINVAL is from setns())
Is this difference intended?
-
Zbyszek
next reply other threads:[~2013-01-20 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 23:36 Zbigniew Jędrzejewski-Szmek [this message]
2013-01-21 0:47 ` is one allowed to reenter a user namespace? Eric W. Biederman
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=20130120233621.GI17370@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=ebiederm@xmission.com \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox