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
..
2010-07-26 13:16:52 -05:00
2010-07-26 13:16:33 -05:00
2009-06-10 17:07:47 +02:00
2010-05-21 18:31:19 -04:00
2009-06-10 17:07:47 +02:00
2010-07-26 13:16:53 -05:00
2009-12-14 23:08:16 -06:00
2009-03-29 09:51:14 +02:00
2007-10-15 16:49:49 +10:00
2009-03-29 09:55:42 +02:00
2007-10-15 16:49:49 +10:00
2008-12-01 11:37:35 +11:00
2010-07-26 13:16:44 -05:00
2010-07-26 16:07:38 -05:00
2009-08-31 14:46:22 -05:00
2010-07-26 13:16:44 -05:00
2010-07-26 13:16:44 -05:00
2010-07-26 13:16:33 -05:00
2010-07-26 13:16:52 -05:00
2010-07-26 13:16:52 -05:00
2010-08-09 16:47:42 -04:00
2010-03-01 16:35:44 -06:00
2009-12-14 23:08:16 -06:00