remarkable-linux/fs/notify
Jan Kara 8581679424 fanotify: Fix use after free for permission events
Currently struct fanotify_event_info has been destroyed immediately
after reporting its contents to userspace. However that is wrong for
permission events because those need to stay around until userspace
provides response which is filled back in fanotify_event_info. So change
to code to free permission events only after we have got the response
from userspace.

Reported-and-tested-by: Jiri Kosina <jkosina@suse.cz>
Reported-and-tested-by: Dave Jones <davej@fedoraproject.org>
Signed-off-by: Jan Kara <jack@suse.cz>
2014-01-29 13:57:17 +01:00
..
dnotify fsnotify: remove pointless NULL initializers 2014-01-21 16:19:41 -08:00
fanotify fanotify: Fix use after free for permission events 2014-01-29 13:57:17 +01:00
inotify fsnotify: Do not return merged event from fsnotify_add_notify_event() 2014-01-29 13:57:10 +01:00
fdinfo.c
fdinfo.h
fsnotify.c fsnotify: remove .should_send_event callback 2014-01-21 16:19:41 -08:00
fsnotify.h
group.c fsnotify: do not share events between notification groups 2014-01-21 16:19:41 -08:00
inode_mark.c hlist: drop the node parameter from iterators 2013-02-27 19:10:24 -08:00
Kconfig
Makefile
mark.c fsnotify: update comments concerning locking scheme 2013-07-09 10:33:20 -07:00
notification.c fsnotify: Do not return merged event from fsnotify_add_notify_event() 2014-01-29 13:57:10 +01:00
vfsmount_mark.c hlist: drop the node parameter from iterators 2013-02-27 19:10:24 -08:00