Jan Kara 0b1b86527d fanotify: fix possible false warning when freeing events ... When freeing permission events by fsnotify_destroy_event(), the warning WARN_ON(!list_empty(&event->list)); may falsely hit. This is because although fanotify_get_response() saw event->response set, there is nothing to make sure the current CPU also sees the removal of the event from the list. Add proper locking around the WARN_ON() to avoid the false warning. Link: http://lkml.kernel.org/r/1473797711-14111-7-git-send-email-jack@suse.cz Reported-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: Jan Kara <jack@suse.cz> Reviewed-by: Lino Sanfilippo <LinoSanfilippo@gmx.de> Cc: Eric Paris <eparis@redhat.com> Cc: Al Viro <viro@ZenIV.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2016-10-07 18:46:26 -07:00
..
dnotify	fsnotify: get rid of fsnotify_destroy_mark_locked()	2015-09-04 16:54:41 -07:00
fanotify	fanotify: use notification_lock instead of access_lock	2016-10-07 18:46:26 -07:00
inotify	fsnotify: convert notification_mutex to a spinlock	2016-10-07 18:46:26 -07:00
fdinfo.c	inotify: hide internal kernel bits from fdinfo	2015-11-05 19:34:48 -08:00
fdinfo.h
fsnotify.c	fsnotify: remove mark->free_list	2015-09-04 16:54:41 -07:00
fsnotify.h	fsnotify: avoid spurious EMFILE errors from inotify_init()	2016-05-19 19:12:14 -07:00
group.c	fsnotify: convert notification_mutex to a spinlock	2016-10-07 18:46:26 -07:00
inode_mark.c	fs/notify/inode_mark.c: use list_next_entry in fsnotify_unmount_inodes	2016-01-14 16:00:49 -08:00
Kconfig
Makefile
mark.c	fsnotify: avoid spurious EMFILE errors from inotify_init()	2016-05-19 19:12:14 -07:00
notification.c	fanotify: fix possible false warning when freeing events	2016-10-07 18:46:26 -07:00
vfsmount_mark.c	fsnotify: remove mark->free_list	2015-09-04 16:54:41 -07:00