From: Richard Weinberger <richard@sigma-star.at>
To: Enrico Weigelt <lkml@metux.net>
Cc: Aleksa Sarai <asarai@suse.de>,
Linux Containers <containers@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: plan9 semantics on Linux - mount namespaces
Date: Wed, 14 Feb 2018 18:50:29 +0100 [thread overview]
Message-ID: <4042675.OEy7g9C5ya@blindfold> (raw)
In-Reply-To: <e924b563-44c6-d678-a6cc-1181f4b820d5@metux.net>
Am Mittwoch, 14. Februar 2018, 18:21:12 CET schrieb Enrico Weigelt:
> On 14.02.2018 16:17, Richard Weinberger wrote:
> > From taking a *very* quick look into busybox source, I suspect this
> > should fix>
> > it:
> >
> > diff --git a/util-linux/unshare.c b/util-linux/unshare.c
> > index 875e3f86e304..3f59cf4d27c2 100644
> > --- a/util-linux/unshare.c
> > +++ b/util-linux/unshare.c
> > @@ -350,9 +350,9 @@ int unshare_main(int argc UNUSED_PARAM, char **argv)
> >
> > * in that user namespace.
> > */
> >
> > xopen_xwrite_close(PATH_PROC_SETGROUPS, "deny");
> >
> > - sprintf(uidmap_buf, "%u 0 1", (unsigned)reuid);
> > + sprintf(uidmap_buf, "0 %u 1", (unsigned)reuid);
> >
> > xopen_xwrite_close(PATH_PROC_UIDMAP, uidmap_buf);
> >
> > - sprintf(uidmap_buf, "%u 0 1", (unsigned)regid);
> > + sprintf(uidmap_buf, "0 %u 1", (unsigned)regid);
> >
> > xopen_xwrite_close(PATH_PROC_GIDMAP, uidmap_buf);
> >
> > } else
> > if (setgrp_str) {
>
> hmm, now it works, but only when strace'ing it.
> that's really strange.
On my box, with my patch applied, also busybox works now.
> But still I wonder whether user_ns really solves my problem, as I don't
> want to create sandboxed users, but only private namespaces just like
> on Plan9.
Well, I'd be surprised if that works out of the box.
Since you're posting on LKML I assumed you're hacking the kernel to support
plan9-alike namespaces...
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2018-02-14 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 22:12 plan9 semantics on Linux - mount namespaces Enrico Weigelt
2018-02-13 22:19 ` Enrico Weigelt
2018-02-13 22:27 ` Aleksa Sarai
2018-02-14 0:01 ` Enrico Weigelt
2018-02-14 4:54 ` Aleksa Sarai
2018-02-14 10:18 ` Enrico Weigelt
2018-02-14 10:24 ` Aleksa Sarai
2018-02-14 11:27 ` Enrico Weigelt
2018-02-14 11:30 ` Richard Weinberger
2018-02-14 12:38 ` Enrico Weigelt
2018-02-14 12:53 ` Richard Weinberger
2018-02-14 14:03 ` Enrico Weigelt
2018-02-14 14:19 ` Richard Weinberger
2018-02-14 15:02 ` Enrico Weigelt
2018-02-14 15:17 ` Richard Weinberger
2018-02-14 17:21 ` Enrico Weigelt
2018-02-14 17:50 ` Richard Weinberger [this message]
2018-02-14 18:01 ` Enrico Weigelt
2018-02-14 18:12 ` Richard Weinberger
2018-02-14 18:32 ` Enrico Weigelt
2018-02-14 20:39 ` Aleksa Sarai
2018-02-16 18:26 ` 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=4042675.OEy7g9C5ya@blindfold \
--to=richard@sigma-star.at \
--cc=asarai@suse.de \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
/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