summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJean-Christophe Dubois <jcd@tribudubois.net>2010-03-23 08:08:09 +0100
committerEric Paris <eparis@redhat.com>2010-07-28 09:59:02 -0400
commit98b5c10d320adfa250c1c18f3ccaec2f78e5e11d (patch)
tree7ca8ca16bea8b514cd416fddb012108e8b74e83a
parent8860f060e473dce1a0873d92105d536f72b05908 (diff)
downloadlinux-98b5c10d320adfa250c1c18f3ccaec2f78e5e11d.tar.gz
linux-98b5c10d320adfa250c1c18f3ccaec2f78e5e11d.tar.bz2
linux-98b5c10d320adfa250c1c18f3ccaec2f78e5e11d.zip
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>
-rw-r--r--fs/notify/fsnotify.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/notify/fsnotify.c b/fs/notify/fsnotify.c
index 668268627894..9810babb1a3b 100644
--- a/fs/notify/fsnotify.c
+++ b/fs/notify/fsnotify.c
@@ -269,7 +269,7 @@ out:
if (event)
fsnotify_put_event(event);
- return 0;
+ return ret;
}
EXPORT_SYMBOL_GPL(fsnotify);