linux.git/fs/proc/inode.c, branch v3.10

proc: Split the namespace stuff out into linux/proc_ns.h

2013-05-01T21:29:39+00:00

Split the proc namespace stuff out into linux/proc_ns.h.

Signed-off-by: David Howells 
cc: netdev@vger.kernel.org
cc: Serge E. Hallyn 
cc: Eric W. Biederman 
Signed-off-by: Al Viro

Include missing linux/magic.h inclusions

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

Include missing linux/magic.h inclusions where the source file is currently
expecting to get magic numbers through linux/proc_fs.h.

Signed-off-by: David Howells 
cc: linux-efi@vger.kernel.org
Signed-off-by: Al Viro

proc: Delete create_proc_read_entry()

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

Delete create_proc_read_entry() as it no longer has any users.

Also delete read_proc_t, write_proc_t, the read_proc member of the
proc_dir_entry struct and the support functions that use them.  This saves a
pointer for every PDE allocated.

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

try a saner locking for pde_opener...

2013-04-09T19:16:52+00:00

Signed-off-by: Al Viro

deal with races between remove_proc_entry() and proc_reg_release()

2013-04-09T19:16:51+00:00

* serialize the call of ->release() on per-pdeo mutex
* don't remove pdeo from per-pde list until we are through with it

Signed-off-by: Al Viro

procfs: preparations for remove_proc_entry() race fixes

2013-04-09T19:16:51+00:00

* leave ->proc_fops alone; make ->pde_users negative instead
* trim pde_opener
* move relevant code in fs/proc/inode.c

Signed-off-by: Al Viro

procfs: don't allow to use proc_create, create_proc_entry, etc. for directories

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

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

vfs,proc: guarantee unique inodes in /proc

2013-03-22T18:44:04+00:00

Dave Jones found another /proc issue with his Trinity tool: thanks to
the namespace model, we can have multiple /proc dentries that point to
the same inode, aliasing directories in /proc//net/ for example.

This ends up being a total disaster, because it acts like hardlinked
directories, and causes locking problems.  We rely on the topological
sort of the inodes pointed to by dentries, and if we have aliased
directories, that odering becomes unreliable.

In short: don't do this.  Multiple dentries with the same (directory)
inode is just a bad idea, and the namespace code should never have
exposed things this way.  But we're kind of stuck with it.

This solves things by just always allocating a new inode during /proc
dentry lookup, instead of using "iget_locked()" to look up existing
inodes by superblock and number.  That actually simplies the code a bit,
at the cost of potentially doing more inode [de]allocations.

That said, the inode lookup wasn't free either (and did a lot of locking
of inodes), so it is probably not that noticeable.  We could easily keep
the old lookup model for non-directory entries, but rather than try to
be excessively clever this just implements the minimal and simplest
workaround for the problem.

Reported-and-tested-by: Dave Jones 
Analyzed-by: Al Viro 
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds

fs/proc: clean up printks

2013-02-28T03:10:11+00:00

- use pr_foo() throughout

- remove a couple of duplicated KERN_WARNINGs, via WARN(KERN_WARNING "...")

- nuke a few warnings which I've never seen happen, ever.

Cc: Joe Perches 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds