All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.rex-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	ebiederm-aS9lmoZGLiVWk0Htik3J/w@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: Mon, 15 Dec 2008 08:29:49 +0100	[thread overview]
Message-ID: <4946076D.7040707@exasol.com> (raw)
In-Reply-To: <20081212015652.1417810800F-Z5GJRQsCWgtQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>

ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12199
> [...]
> You specified NEWNS  in your clone flags, creating a new mount namespace
> as well.
> 
> Your executable came from a different mount namespace and thus has a different
> set of mounts.  Which defeats the logic in d_path to honor current->fs->root
> because your executable came from a different universe.
> 
> No bugs here just weird corner cases with the mount namespace.
> 
> Eric

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.

Robert

       reply	other threads:[~2008-12-15  7:29 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   ` robert.rex-GD4dBWQXeU/QT0dZR+AlfA [this message]
     [not found]     ` <4946076D.7040707-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org>
2008-12-15  7:44       ` [Bug 12199] /proc/1/exe entry of PID namespace init process links to wrong executable 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=4946076D.7040707@exasol.com \
    --to=robert.rex-gd4dbwqxeu/qt0dzr+alfa@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=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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.