Eric Paris c05594b621 fsnotify: fix inotify tail drop check with path entries ... fsnotify drops new events when they are the same as the tail event on the queue to be sent to userspace. The problem is that if the event comes with a path we forget to break out of the switch statement and fall into the code path which matches on events that do not have any type of file backed information (things like IN_UNMOUNT and IN_Q_OVERFLOW). The problem is that this code thinks all such events should be dropped. Fix is to add a break. Signed-off-by: Eric Paris <eparis@redhat.com>		2009-07-21 15:26:26 -04:00
..
dnotify	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -04:00
inotify	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -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: allow groups to set freeing_mark to null	2009-06-11 14:57:55 -04:00
Kconfig	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -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: fix inotify tail drop check with path entries	2009-07-21 15:26:26 -04:00