kernel-ark/fs/proc
Al Viro 831830b5a2 restrict reading from /proc/<pid>/maps to those who share ->mm or can ptrace pid
Contents of /proc/*/maps is sensitive and may become sensitive after
open() (e.g.  if target originally shares our ->mm and later does exec
on suid-root binary).

Check at read() (actually, ->start() of iterator) time that mm_struct
we'd grabbed and locked is
 - still the ->mm of target
 - equal to reader's ->mm or the target is ptracable by reader.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Acked-by: Rik van Riel <riel@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-01-02 13:13:27 -08:00
..
array.c
base.c restrict reading from /proc/<pid>/maps to those who share ->mm or can ptrace pid 2008-01-02 13:13:27 -08:00
generic.c proc: remove/Fix proc generic d_revalidate 2007-12-10 19:43:55 -08:00
inode-alloc.txt
inode.c proc: fix proc_dir_entry refcounting 2007-12-05 09:21:20 -08:00
internal.h restrict reading from /proc/<pid>/maps to those who share ->mm or can ptrace pid 2008-01-02 13:13:27 -08:00
kcore.c
kmsg.c
Makefile
mmu.c
nommu.c
proc_devtree.c
proc_misc.c Unify /proc/slabinfo configuration 2008-01-02 13:04:48 -08:00
proc_net.c
proc_sysctl.c
proc_tty.c
root.c proc: fix proc_dir_entry refcounting 2007-12-05 09:21:20 -08:00
task_mmu.c restrict reading from /proc/<pid>/maps to those who share ->mm or can ptrace pid 2008-01-02 13:13:27 -08:00
task_nommu.c restrict reading from /proc/<pid>/maps to those who share ->mm or can ptrace pid 2008-01-02 13:13:27 -08:00
vmcore.c