Eric Paris 5f3f259fa8 fsnotify: reset used_inode and used_vfsmount on each pass ... The fsnotify main loop has 2 booleans which tell if a particular mark was sent to the listeners or if it should be processed in the next pass. The problem is that the booleans were not reset on each traversal of the loop. So marks could get skipped even when they were not sent to the notifiers. Reported-by: Tvrtko Ursulin <tvrtko.ursulin@sophos.com> Signed-off-by: Eric Paris <eparis@redhat.com>		2010-08-22 20:09:41 -04:00
..
dnotify	fanotify: use both marks when possible	2010-07-28 10:18:55 -04:00
fanotify	Revert "fsnotify: store struct file not struct path"	2010-08-12 14:23:04 -07:00
inotify	Revert "fsnotify: store struct file not struct path"	2010-08-12 14:23:04 -07:00
fsnotify.c	fsnotify: reset used_inode and used_vfsmount on each pass	2010-08-22 20:09:41 -04:00
fsnotify.h	fsnotify: remove global fsnotify groups lists	2010-07-28 10:18:54 -04:00
group.c	fsnotify: remove global fsnotify groups lists	2010-07-28 10:18:54 -04:00
inode_mark.c	Merge branch 'for-linus' of git://git.infradead.org/users/eparis/notify	2010-08-10 11:39:13 -07: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	fsnotify: remove global fsnotify groups lists	2010-07-28 10:18:54 -04:00
notification.c	Revert "fsnotify: store struct file not struct path"	2010-08-12 14:23:04 -07:00
vfsmount_mark.c	fsnotify: use an explicit flag to indicate fsnotify_destroy_mark has been called	2010-07-28 10:18:52 -04:00