Jan Kara 9cf90cef36 fsnotify: Protect bail out path of fsnotify_add_mark_locked() properly ... When fsnotify_add_mark_locked() fails it cleans up the mark it was adding. Since the mark is already visible in group's list, we should protect update of mark->flags with mark->lock. I'm not aware of any real issues this could cause (since we also hold group->mark_mutex) but better be safe and obey locking rules properly. Reviewed-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz>		2017-10-31 17:54:56 +01:00
..
dnotify	dnotify: Handle errors from fsnotify_add_mark_locked() in fcntl_dirnotify()	2017-10-31 17:41:04 +01:00
fanotify	fanotify: don't expose EOPENSTALE to userspace	2017-04-25 15:48:06 +02:00
inotify	fsnotify: Move ->free_mark callback to fsnotify_ops	2017-04-10 17:37:36 +02:00
fdinfo.c	fsnotify: Move object pointer to fsnotify_mark_connector	2017-04-10 17:37:35 +02:00
fdinfo.h	fs: Convert show_fdinfo functions to void	2014-11-05 14:13:23 -05:00
fsnotify.c	dentry name snapshots	2017-07-07 20:09:10 -04:00
fsnotify.h	fsnotify: Remove fsnotify_find_{inode|vfsmount}_mark()	2017-04-10 17:37:36 +02:00
group.c	fsnotify: Remove fsnotify_detach_group_marks()	2017-04-10 17:37:36 +02:00
Kconfig	rcu: Make SRCU optional by using CONFIG_SRCU	2015-01-06 11:04:29 -08:00
Makefile	fsnotify: Drop inode_mark.c	2017-04-10 17:37:36 +02:00
mark.c	fsnotify: Protect bail out path of fsnotify_add_mark_locked() properly	2017-10-31 17:54:56 +01:00
notification.c	fsnotify: clean up spinlock assertions	2016-10-07 18:46:26 -07:00