aboutsummaryrefslogtreecommitdiff
path: root/fs/proc/self.c
AgeCommit message (Collapse)AuthorFilesLines
2014-04-01new helper: readlink_copy()Al Viro1-1/+1
Signed-off-by: Al Viro <[email protected]>
2013-10-24new helper: kfree_put_link()Al Viro1-9/+1
duplicated to hell and back... Signed-off-by: Al Viro <[email protected]>
2013-04-29Include missing linux/slab.h inclusionsDavid Howells1-0/+1
Include missing linux/slab.h inclusions where the source file is currently expecting to get kmalloc() and co. through linux/proc_fs.h. Signed-off-by: David Howells <[email protected]> Acked-by: Greg Kroah-Hartman <[email protected]> cc: [email protected] cc: [email protected] cc: [email protected] cc: [email protected] cc: [email protected] cc: [email protected] Signed-off-by: Al Viro <[email protected]>
2013-04-09procfs: switch /proc/self away from proc_dir_entryAl Viro1-7/+39
Just have it pinned in dcache all along and let procfs ->kill_sb() drop it before kill_anon_super(). Signed-off-by: Al Viro <[email protected]>
2013-04-09mode_t, whack-a-mole at 11...Al Viro1-1/+1
Signed-off-by: Al Viro <[email protected]>
2012-11-19procfs: Use the proc generic infrastructure for proc/self.Eric W. Biederman1-0/+59
I had visions at one point of splitting proc into two filesystems. If that had happened proc/self being the the part of proc that actually deals with pids would have been a nice cleanup. As it is proc/self requires a lot of unnecessary infrastructure for a single file. The only user visible change is that a mounted /proc for a pid namespace that is dead now shows a broken proc symlink, instead of being completely invisible. I don't think anyone will notice or care. Signed-off-by: Eric W. Biederman <[email protected]>