]> bbs.cooldavid.org Git - net-next-2.6.git/commit
git://bbs.cooldavid.org / net-next-2.6.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8860f06) | patch
fanotify: do not always return 0 in fsnotify
authorJean-Christophe Dubois <jcd@tribudubois.net>
Tue, 23 Mar 2010 07:08:09 +0000 (08:08 +0100)
committerEric Paris <eparis@redhat.com>
Wed, 28 Jul 2010 13:59:02 +0000 (09:59 -0400)
commit98b5c10d320adfa250c1c18f3ccaec2f78e5e11d
tree7ca8ca16bea8b514cd416fddb012108e8b74e83atree | snapshot (tar.bz2 tar.gz zip)
parent8860f060e473dce1a0873d92105d536f72b05908commit | diff
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>
fs/notify/fsnotify.c diff | blob | blame | history
Clone of davem's net-next-2.6 tree