Alexey Dobriyan 99b7623380 proc 2/2: remove struct proc_dir_entry::owner ... Setting ->owner as done currently (pde->owner = THIS_MODULE) is racy as correctly noted at bug #12454. Someone can lookup entry with NULL ->owner, thus not pinning enything, and release it later resulting in module refcount underflow. We can keep ->owner and supply it at registration time like ->proc_fops and ->data. But this leaves ->owner as easy-manipulative field (just one C assignment) and somebody will forget to unpin previous/pin current module when switching ->owner. ->proc_fops is declared as "const" which should give some thoughts. ->read_proc/->write_proc were just fixed to not require ->owner for protection. rmmod'ed directories will be empty and return "." and ".." -- no harm. And directories with tricky enough readdir and lookup shouldn't be modular. We definitely don't want such modular code. Removing ->owner will also make PDE smaller. So, let's nuke it. Kudos to Jeff Layton for reminding about this, let's say, oversight. http://bugzilla.kernel.org/show_bug.cgi?id=12454 Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>		2009-03-31 01:14:44 +04:00
..
afs_cm.h
afs_fs.h
afs_vl.h
afs.h
cache.c
cache.h
callback.c
cell.c
cmservice.c
dir.c	constify dentry_operations: AFS	2009-03-27 14:44:00 -04:00
file.c	afs: convert to new aops	2008-10-16 11:21:48 -07:00
flock.c
fsclient.c
inode.c
internal.h	afs: convert to new aops	2008-10-16 11:21:48 -07:00
Kconfig	fs/Kconfig: move afs out	2009-01-22 13:16:01 +03:00
main.c
Makefile
misc.c
mntpt.c	[PATCH] pass struct path * to do_add_mount()	2008-08-01 11:25:32 -04:00
netdevices.c
proc.c	proc 2/2: remove struct proc_dir_entry::owner	2009-03-31 01:14:44 +04:00
rxrpc.c
security.c
server.c	fs: replace NIPQUAD()	2008-10-31 00:56:28 -07:00
super.c	vfs: Use const for kernel parser table	2008-10-13 10:10:37 -07:00
vlclient.c
vlocation.c
vnode.c
volume.c
write.c	fs: symlink write_begin allocation context fix	2009-01-04 13:33:20 -08:00