From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Emelyanov Subject: Re: [RFC] fs, proc: Introduce the /proc//map_files/ directory v2 Date: Thu, 25 Aug 2011 10:42:44 +0400 Message-ID: <4E55EEE4.4050902@parallels.com> References: <20110824085329.GL29452@sun> <4E551331.1010709@acm.org> <4E551693.5030400@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Zan Lynx , Cyrill Gorcunov , Nathan Lynch , Oren Laadan , Daniel Lezcano , Tejun Heo , Andrew Morton , Glauber Costa , "containers@lists.osdl.org" , "linux-kernel@vger.kernel.org" , Serge Hallyn , LINUXFS-ML , James Bottomley To: Andi Kleen Return-path: Received: from mailhub.sw.ru ([195.214.232.25]:27565 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752912Ab1HYGmz (ORCPT ); Thu, 25 Aug 2011 02:42:55 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 08/24/2011 09:36 PM, Andi Kleen wrote: > Pavel Emelyanov writes: >> >> No and this is the trick - when you readlink it - it give you trash, but >> when you open one - you get exactly the same file as the map points to. > > Isn't that a minor security hole? > > For example if I pass a file descriptor into a chroot process for > reading, and with this interface you can open it for writing too. > I could see this causing problems. How does it differ from the /proc/pid/fd links? > -Andi >