linux-toradex.git/fs/proc/self.c, branch v4.4.77

don't pass nameidata to ->follow_link()

2015-05-11T02:20:15+00:00

its only use is getting passed to nd_jump_link(), which can obtain
it from current->nameidata

Signed-off-by: Al Viro

new ->follow_link() and ->put_link() calling conventions

2015-05-11T02:19:45+00:00

a) instead of storing the symlink body (via nd_set_link()) and returning
an opaque pointer later passed to ->put_link(), ->follow_link() _stores_
that opaque pointer (into void * passed by address by caller) and returns
the symlink body.  Returning ERR_PTR() on error, NULL on jump (procfs magic
symlinks) and pointer to symlink body for normal symlinks.  Stored pointer
is ignored in all cases except the last one.

Storing NULL for opaque pointer (or not storing it at all) means no call
of ->put_link().

b) the body used to be passed to ->put_link() implicitly (via nameidata).
Now only the opaque pointer is.  In the cases when we used the symlink body
to free stuff, ->follow_link() now should store it as opaque pointer in addition
to returning it.

Signed-off-by: Al Viro

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells 
Signed-off-by: Al Viro

new helper: readlink_copy()

2014-04-02T03:19:15+00:00

Signed-off-by: Al Viro

new helper: kfree_put_link()

2013-10-25T03:34:49+00:00

duplicated to hell and back...

Signed-off-by: Al Viro

Include missing linux/slab.h inclusions

2013-04-29T19:42:01+00:00

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 
Acked-by: Greg Kroah-Hartman 
cc: linux-s390@vger.kernel.org
cc: sparclinux@vger.kernel.org
cc: linux-efi@vger.kernel.org
cc: linux-mtd@lists.infradead.org
cc: devel@driverdev.osuosl.org
cc: x86@kernel.org
Signed-off-by: Al Viro

procfs: switch /proc/self away from proc_dir_entry

2013-04-09T18:13:05+00:00

Just have it pinned in dcache all along and let procfs ->kill_sb()
drop it before kill_anon_super().

Signed-off-by: Al Viro

mode_t, whack-a-mole at 11...

2013-04-09T18:13:05+00:00

Signed-off-by: Al Viro

procfs: Use the proc generic infrastructure for proc/self.

2012-11-19T11:09:34+00:00

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