Eric Paris e42e27736d inotify/dnotify: should_send_event shouldn't match on FS_EVENT_ON_CHILD ...

inotify and dnotify will both indicate that they want any event which came
from a child inode.  The fix is to mask off FS_EVENT_ON_CHILD when deciding
if inotify or dnotify is interested in a given event.

Signed-off-by: Eric Paris <eparis@redhat.com>

2009-06-11 14:57:54 -04:00

..

dnotify

inotify/dnotify: should_send_event shouldn't match on FS_EVENT_ON_CHILD

2009-06-11 14:57:54 -04:00

inotify

inotify/dnotify: should_send_event shouldn't match on FS_EVENT_ON_CHILD

2009-06-11 14:57:54 -04:00

fsnotify.c

inotify/dnotify: should_send_event shouldn't match on FS_EVENT_ON_CHILD

2009-06-11 14:57:54 -04:00

fsnotify.h

fsnotify: generic notification queue and waitq

2009-06-11 14:57:53 -04:00

group.c

fsnotify: generic notification queue and waitq

2009-06-11 14:57:53 -04:00

inode_mark.c

fsnotify: handle filesystem unmounts with fsnotify marks

2009-06-11 14:57:54 -04:00

Kconfig

fsnotify: unified filesystem notification backend

2009-06-11 14:57:52 -04:00

Makefile

fsnotify: add marks to inodes so groups can interpret how to handle those inodes

2009-06-11 14:57:53 -04:00

notification.c

fsnotify: allow groups to add private data to events

2009-06-11 14:57:54 -04:00