Messages in this thread |  | | Date | Thu, 25 Aug 2011 18:47:47 +0400 | | From | Pavel Emelyanov <> | | Subject | Re: [RFC] fs, proc: Introduce the /proc/<pid>/map_files/ directory v2 |
| |
On 08/25/2011 06:04 PM, Andi Kleen wrote: > On Thu, Aug 25, 2011 at 10:42:44AM +0400, Pavel Emelyanov wrote: >> On 08/24/2011 09:36 PM, Andi Kleen wrote: >>> Pavel Emelyanov <xemul@parallels.com> 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? > > Those cannot be opened I thought.
Neither can be these links then - I use the same access checks in my code.
> -Andi >
|  |