simplify checks for I_CLEAR/I_FREEING
authorAl Viro <viro@zeniv.linux.org.uk>
Wed, 2 Jun 2010 21:38:30 +0000 (17:38 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 9 Aug 2010 20:47:44 +0000 (16:47 -0400)
commita4ffdde6e56fdf8c34ddadc2674d6eb978083369
tree0fa07df92d804cb7d0482135195e4835cb16403a
parentb5fc510c48f631882ccec3c0f02a25d5b67de09f
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>
fs/btrfs/inode.c
fs/drop_caches.c
fs/fs-writeback.c
fs/gfs2/inode.c
fs/inode.c
fs/nilfs2/gcdat.c
fs/notify/inode_mark.c
fs/notify/inotify/inotify.c
fs/quota/dquot.c
fs/xfs/linux-2.6/xfs_iops.c
include/linux/fs.h