Lino Sanfilippo 1734dee4e3 fanotify: Dont allow a mask of 0 if setting or removing a mark ... In mark_remove_from_mask() we destroy marks that have their event mask cleared. Thus we should not allow the creation of those marks in the first place. With this patch we check if the mask given from user is 0 in case of FAN_MARK_ADD. If so we return an error. Same for FAN_MARK_REMOVE since this does not have any effect. Signed-off-by: Lino Sanfilippo <LinoSanfilippo@gmx.de> Signed-off-by: Eric Paris <eparis@redhat.com>		2010-12-07 16:14:21 -05:00
..
dnotify	fanotify: use both marks when possible	2010-07-28 10:18:55 -04:00
fanotify	fanotify: Dont allow a mask of 0 if setting or removing a mark	2010-12-07 16:14:21 -05:00
inotify	fsnotify: rename FS_IN_ISDIR to FS_ISDIR	2010-10-28 17:22:15 -04:00
fsnotify.c	fsnotify: call fsnotify_parent in perm events	2010-10-28 17:22:13 -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	fsnotify: implement ordering between notifiers	2010-10-28 17:22:13 -04:00
Kconfig	fanotify: allow fanotify to be built	2010-10-28 17:22:13 -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: implement ordering between notifiers	2010-10-28 17:22:13 -04:00