lkml.org 
[lkml]   [2011]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] fs, proc: Introduce the /proc/<pid>/map_files/ directory v2
On Wed, Aug 24, 2011 at 09:05:21AM -0600, Zan Lynx wrote:
> On 8/24/2011 2:53 AM, Cyrill Gorcunov wrote:
> > From: Pavel Emelyanov <xemul@parallels.com>
> >
> > This one behaves similarly to the /proc/<pid>/fd/ one - it contains symlinks
> > one for each mapping with file, the name of a symlink is vma->vm_start, the
> > target is the file. Opening a symlink results in a file that point exactly
> > to the same inode as them vma's one.
> >
> > This thing is aimed to help checkpointing processes.
> >
> > For example the ls -l of some arbitrary /proc/<pid>/map_files/
> >
> > | lr-x------ 1 cyrill cyrill 64 Aug 9 15:25 0x3d73a00000 -> /lib64/ld-2.5.so
> [snip]
>
> Just curious: How do these symlinks work when the process reading a
> /proc file is in a chroot or a different namespace?
>
> For example, a chroot environment might have independent copies of
> /lib64/ld-2.5.so and a bind mount of /proc. Does the symlink then point
> to the wrong file?

To be fair, I personally didn't tried such scenario but it should be
the same behaviour as for /proc/$pid/fd since data is taken from
a task pointed by pid. I'll check though, good question.

Cyrill


\
 
 \ /
  Last update: 2011-08-24 17:25    [W:0.139 / U:0.388 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site