From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch 2/2] fs, proc: Introduce the /proc//map_files/ directory v12 Date: Tue, 13 Sep 2011 23:52:22 -0700 Message-ID: <20110913235222.043927b3.akpm@linux-foundation.org> References: <20110913211359.674453213@openvz.org> <20110913212447.918816776@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110913212447.918816776@openvz.org> Sender: linux-fsdevel-owner@vger.kernel.org To: Cyrill Gorcunov Cc: linux-kernel@vger.kernel.org, containers@lists.osdl.org, linux-fsdevel@vger.kernel.org, Kirill Shutemov , Pavel Emelyanov , James Bottomley , Nathan Lynch , Zan Lynx , Daniel Lezcano , Vasiliy Kulikov , Tejun Heo , Alexey Dobriyan , Al Viro , Andrew Morton List-Id: containers.vger.kernel.org On Wed, 14 Sep 2011 01:14:01 +0400 Cyrill Gorcunov wrote: > This one behaves similarly to the /proc//fd/ one - it contains symlinks > one for each mapping with file, the name of a symlink is "vma->vm_start-vma->vm_end", > the target is the file. Opening a symlink results in a file that point exactly > to the same inode as them vma's one. We should fully work through Pavel Machek's comments, please. For some reason I'm a bit paranoid about security lately :(