Al Viro a4ffdde6e5 simplify checks for I_CLEAR/I_FREEING ... add I_CLEAR instead of replacing I_FREEING with it. I_CLEAR is equivalent to I_FREEING for almost all code looking at either; it's there to keep track of having called clear_inode() exactly once per inode lifetime, at some point after having set I_FREEING. I_CLEAR and I_FREEING never get set at the same time with the current code, so we can switch to setting i_flags to I_FREEING | I_CLEAR instead of I_CLEAR without loss of information. As the result of such change, checks become simpler and the amount of code that needs to know about I_CLEAR shrinks a lot. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>		2010-08-09 16:47:44 -04:00
..
dnotify	dnotify: ignore FS_EVENT_ON_CHILD	2009-10-20 18:02:33 -04:00
inotify	simplify checks for I_CLEAR/I_FREEING	2010-08-09 16:47:44 -04:00
fsnotify.c	include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h	2010-03-30 22:02:32 +09:00
fsnotify.h	fsnotify: generic notification queue and waitq	2009-06-11 14:57:53 -04:00
group.c	fsnotify: generic notification queue and waitq	2009-06-11 14:57:53 -04:00
inode_mark.c	simplify checks for I_CLEAR/I_FREEING	2010-08-09 16:47:44 -04:00
Kconfig	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -04:00
Makefile	fsnotify: add marks to inodes so groups can interpret how to handle those inodes	2009-06-11 14:57:53 -04:00
notification.c	inotify: fix coalesce duplicate events into a single event in special case	2009-10-18 15:49:38 -04:00