linux-toradex.git/fs/notify/fsnotify.c, branch v3.7.2 Linux kernel for Apalis and Colibri modules vfs: switch i_dentry/d_alias to hlist 2012-07-14T12:32:55+00:00 Al Viro viro@zeniv.linux.org.uk 2012-06-09T17:51:19+00:00 b3d9b7a3c752dc4b6976a4ff7b8298887a5b734d Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fsnotify: remove unused parameter from send_to_group() 2012-05-31T01:04:53+00:00 Dan Carpenter dan.carpenter@oracle.com 2012-05-29T18:02:24+00:00 fd657170c039a918c0b46f51db8005317d4c83fa We don't use "mnt" anymore in send_to_group() after 1968f5eed5 ("fanotify: use both marks when possible") was applied. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 
We don't use "mnt" anymore in send_to_group() after 1968f5eed5 ("fanotify:
use both marks when possible") was applied.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
vfs: move fsnotify junk to struct mount 2012-01-04T03:57:12+00:00 Al Viro viro@zeniv.linux.org.uk 2011-11-25T07:35:16+00:00 c63181e6b6df89176b3984c6977bb5ec03d0df23 Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs: dcache per-inode inode alias locking 2011-01-07T06:50:31+00:00 Nick Piggin npiggin@kernel.dk 2011-01-07T06:50:06+00:00 873feea09ebc980cbd3631b767356ce1eee65ec1 dcache_inode_lock can be replaced with per-inode locking. Use existing inode->i_lock for this. This is slightly non-trivial because we sometimes need to find the inode from the dentry, which requires d_inode to be stabilised (either with refcount or d_lock). Signed-off-by: Nick Piggin <npiggin@kernel.dk> 
dcache_inode_lock can be replaced with per-inode locking. Use existing
inode->i_lock for this. This is slightly non-trivial because we sometimes
need to find the inode from the dentry, which requires d_inode to be
stabilised (either with refcount or d_lock).

Signed-off-by: Nick Piggin <npiggin@kernel.dk>
fs: dcache remove dcache_lock 2011-01-07T06:50:23+00:00 Nick Piggin npiggin@kernel.dk 2011-01-07T06:49:38+00:00 b5c84bf6f6fa3a7dfdcb556023a62953574b60ee dcache_lock no longer protects anything. remove it. Signed-off-by: Nick Piggin <npiggin@kernel.dk> 
dcache_lock no longer protects anything. remove it.

Signed-off-by: Nick Piggin <npiggin@kernel.dk>
fs: scale inode alias list 2011-01-07T06:50:22+00:00 Nick Piggin npiggin@kernel.dk 2011-01-07T06:49:35+00:00 b23fb0a60379a95e10c671f646b259ea2558421e Add a new lock, dcache_inode_lock, to protect the inode's i_dentry list from concurrent modification. d_alias is also protected by d_lock. Signed-off-by: Nick Piggin <npiggin@kernel.dk> 
Add a new lock, dcache_inode_lock, to protect the inode's i_dentry list
from concurrent modification. d_alias is also protected by d_lock.

Signed-off-by: Nick Piggin <npiggin@kernel.dk>
fs: dcache scale subdirs 2011-01-07T06:50:21+00:00 Nick Piggin npiggin@kernel.dk 2011-01-07T06:49:34+00:00 2fd6b7f50797f2e993eea59e0a0b8c6399c811dc Protect d_subdirs and d_child with d_lock, except in filesystems that aren't using dcache_lock for these anyway (eg. using i_mutex). Note: if we change the locking rule in future so that ->d_child protection is provided only with ->d_parent->d_lock, it may allow us to reduce some locking. But it would be an exception to an otherwise regular locking scheme, so we'd have to see some good results. Probably not worthwhile. Signed-off-by: Nick Piggin <npiggin@kernel.dk> 
Protect d_subdirs and d_child with d_lock, except in filesystems that aren't
using dcache_lock for these anyway (eg. using i_mutex).

Note: if we change the locking rule in future so that ->d_child protection is
provided only with ->d_parent->d_lock, it may allow us to reduce some locking.
But it would be an exception to an otherwise regular locking scheme, so we'd
have to see some good results. Probably not worthwhile.

Signed-off-by: Nick Piggin <npiggin@kernel.dk>
fsnotify: call fsnotify_parent in perm events 2010-10-28T21:22:13+00:00 Eric Paris eparis@redhat.com 2010-10-28T21:21:56+00:00 52420392c81c8712f555e6bcd116d8bd214ce43a fsnotify perm events do not call fsnotify parent. That means you cannot register a perm event on a directory and enforce permissions on all inodes in that directory. This patch fixes that situation. Signed-off-by: Eric Paris <eparis@redhat.com> 
fsnotify perm events do not call fsnotify parent.  That means you cannot
register a perm event on a directory and enforce permissions on all inodes in
that directory.  This patch fixes that situation.

Signed-off-by: Eric Paris <eparis@redhat.com>
fsnotify: correctly handle return codes from listeners 2010-10-28T21:22:13+00:00 Eric Paris eparis@redhat.com 2010-10-28T21:21:56+00:00 ff8bcbd03da881bf1171910c6c07d44bd3c0a234 When fsnotify groups return errors they are ignored. For permissions events these should be passed back up the stack, but for most events these should continue to be ignored. Signed-off-by: Eric Paris <eparis@redhat.com> 
When fsnotify groups return errors they are ignored.  For permissions
events these should be passed back up the stack, but for most events these
should continue to be ignored.

Signed-off-by: Eric Paris <eparis@redhat.com>
fsnotify: use dget_parent 2010-10-26T01:26:14+00:00 Christoph Hellwig hch@infradead.org 2010-10-10T09:36:30+00:00 4d4eb36679adbdd75495e1bbfe7ac40e4ae41dea Use dget_parent instead of opencoding it. This simplifies the code, but more importanly prepares for the more complicated locking for a parent dget in the dcache scale patch series. It means we do grab a reference to the parent now if need to be watched, but not with the specified mask. If this turns out to be a problem we'll have to revisit it, but for now let's keep as much as possible dcache internals inside dcache.[ch]. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 
Use dget_parent instead of opencoding it.  This simplifies the code, but
more importanly prepares for the more complicated locking for a parent
dget in the dcache scale patch series.

It means we do grab a reference to the parent now if need to be watched,
but not with the specified mask.  If this turns out to be a problem
we'll have to revisit it, but for now let's keep as much as possible
dcache internals inside dcache.[ch].

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>