All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [Bug 12199] /proc/1/exe entry of PID namespace init process links to wrong executable
       [not found] ` <20081212015652.1417810800F-Z5GJRQsCWgtQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
@ 2008-12-15  7:29   ` robert.rex-GD4dBWQXeU/QT0dZR+AlfA
       [not found]     ` <4946076D.7040707-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: robert.rex-GD4dBWQXeU/QT0dZR+AlfA @ 2008-12-15  7:29 UTC (permalink / raw)
  To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b
  Cc: containers-qjLDD68F18O7TbgM5vRIOg,
	sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8,
	ebiederm-aS9lmoZGLiVWk0Htik3J/w,
	bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Bug 12199] /proc/1/exe entry of PID namespace init process links to wrong executable
       [not found]     ` <4946076D.7040707-GD4dBWQXeU/QT0dZR+AlfA@public.gmane.org>
@ 2008-12-15  7:44       ` Eric W. Biederman
  0 siblings, 0 replies; 2+ messages in thread
From: Eric W. Biederman @ 2008-12-15  7:44 UTC (permalink / raw)
  To: robert.rex-GD4dBWQXeU/QT0dZR+AlfA
  Cc: containers-qjLDD68F18O7TbgM5vRIOg,
	akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b,
	sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8,
	bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-12-15  7:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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 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.