Eric Paris 3bcf3860a4 fsnotify: store struct file not struct path ... Al explains that calling dentry_open() with a mnt/dentry pair is only garunteed to be safe if they are already used in an open struct file. To make sure this is the case don't store and use a struct path in fsnotify, always use a struct file. Signed-off-by: Eric Paris <eparis@redhat.com>		2010-07-28 10:18:51 -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	fanotify: clear all fanotify marks	2010-07-28 09:59:00 -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: call iput on inodes when no longer marked	2010-07-28 09:59:02 -04:00
notification.c	fsnotify: store struct file not struct path	2010-07-28 10:18:51 -04:00
vfsmount_mark.c	fsnotify: update gfp/slab.h includes	2010-07-28 09:59:03 -04:00