From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: robert.rex-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
Subject: Re: [Bug 12199] /proc/1/exe entry of PID namespace init process links to wrong executable
Date: Sun, 14 Dec 2008 23:44:59 -0800 [thread overview]
Message-ID: <m1r649anlw.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <4946076D.7040707-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org> (robert rex's message of "Mon, 15 Dec 2008 08:29:49 +0100")
robert.rex-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org writes:
> Thanks for your analysis! That sounds reasonable (I didn't recognize the use of
> CLONE_NEWNS - just pasting from the examples ;-) - but I needed it to mount a
> proc filesystem in the new PID namespace while using the other one
> "outside"). So, I may not count on the /proc/{PID}/exe link anymore in such
> cases as far as I see.
Just setup the mount namespace instead of setting up a chroot and all will be well.
Eric
prev parent reply other threads:[~2008-12-15 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081212015652.1417810800F@picon.linux-foundation.org>
[not found] ` <20081212015652.1417810800F-Z5GJRQsCWgtQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2008-12-15 7:29 ` [Bug 12199] /proc/1/exe entry of PID namespace init process links to wrong executable robert.rex-GD4dBWQXeU/QT0dZR+AlfA
[not found] ` <4946076D.7040707-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org>
2008-12-15 7:44 ` Eric W. Biederman [this message]
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=m1r649anlw.fsf@frodo.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=robert.rex-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.