Jean-Christophe Dubois 98b5c10d32 fanotify: do not always return 0 in fsnotify ...

It seems to me you are always returning 0 in fsnotify, when you should return
the error (EPERM) returned by fanotify.

Signed-off-by: Jean-Christophe DUBOIS <jcd@tribudubois.net>
Signed-off-by: Eric Paris <eparis@redhat.com>

2010-07-28 09:59:02 -04:00

..

dnotify

fsnotify: allow marks to not pin inodes in core

2010-07-28 09:58:59 -04:00

fanotify

fanotify: do not return 0 in a void function

2010-07-28 09:59:02 -04:00

inotify

fsnotify: intoduce a notification merge argument

2010-07-28 09:59:01 -04:00

fsnotify.c

fanotify: do not always return 0 in fsnotify

2010-07-28 09:59:02 -04:00

fsnotify.h

fsnotify: allow marks to not pin inodes in core

2010-07-28 09:58:59 -04:00

group.c

fsnotify: add group priorities

2010-07-28 09:59:01 -04:00

inode_mark.c

fanotify: clear all fanotify marks

2010-07-28 09:59:00 -04:00

Kconfig

fanotify: fscking all notification system

2010-07-28 09:58:54 -04:00

Makefile

fsnotify: vfsmount marks generic functions

2010-07-28 09:58:57 -04:00

mark.c

fanotify: clear all fanotify marks

2010-07-28 09:59:00 -04:00

notification.c

fsnotify: use unsigned char * for dentry->d_name.name

2010-07-28 09:59:01 -04:00

vfsmount_mark.c

fanotify: clear all fanotify marks

2010-07-28 09:59:00 -04:00