kpriv/linux-hardened
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
linux-hardened/fs/notify
History
Eric Paris 700307a29a fsnotify: use an explicit flag to indicate fsnotify_destroy_mark has been called 
Currently fsnotify check is mark->group is NULL to decide if
fsnotify_destroy_mark() has already been called or not.  With the upcoming
rcu work it is a heck of a lot easier to use an explicit flag than worry
about group being set to NULL.

Signed-off-by: Eric Paris <eparis@redhat.com>
2010-07-28 10:18:52 -04:00
..
dnotify fsnotify: allow marks to not pin inodes in core 2010-07-28 09:58:59 -04:00
fanotify fsnotify: store struct file not struct path 2010-07-28 10:18:51 -04:00
inotify fsnotify: store struct file not struct path 2010-07-28 10:18:51 -04:00
fsnotify.c fsnotify: store struct file not struct path 2010-07-28 10:18:51 -04:00
fsnotify.h fsnotify: allow marks to not pin inodes in core 2010-07-28 09:58:59 -04:00
group.c fanotify: drop the useless priority argument 2010-07-28 09:59:03 -04:00
inode_mark.c fsnotify: use an explicit flag to indicate fsnotify_destroy_mark has been called 2010-07-28 10:18:52 -04: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: use an explicit flag to indicate fsnotify_destroy_mark has been called 2010-07-28 10:18:52 -04:00
notification.c vfs/fsnotify: fsnotify_close can delay the final work in fput 2010-07-28 10:18:51 -04: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