Dave Chinner 250df6ed27 fs: protect inode->i_state with inode->i_lock
Protect inode state transitions and validity checks with the
inode->i_lock. This enables us to make inode state transitions
independently of the inode_lock and is the first step to peeling
away the inode_lock from the code.

This requires that __iget() is done atomically with i_state checks
during list traversals so that we don't race with another thread
marking the inode I_FREEING between the state check and grabbing the
reference.

Also remove the unlock_new_inode() memory barrier optimisation
required to avoid taking the inode_lock when clearing I_NEW.
Simplify the code by simply taking the inode->i_lock around the
state change and wakeup. Because the wakeup is no longer tricky,
remove the wake_up_inode() function and open code the wakeup where
necessary.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2011-03-24 21:16:31 -04:00
..
2011-03-17 14:02:57 +01:00
2011-02-25 11:12:37 -08:00
2011-02-21 22:31:47 +00:00
2011-03-10 13:22:34 -06:00
2011-03-03 01:28:17 -05:00
2011-01-14 09:23:36 -08:00
2011-03-02 22:27:36 +01:00
2011-03-17 14:02:57 +01:00
2011-03-21 00:45:50 -04:00
2011-03-17 14:02:57 +01:00
2011-03-03 01:28:16 -05:00
2011-03-23 19:46:19 -07:00
2011-03-23 19:46:19 -07:00
2011-03-21 00:16:09 -04:00
2011-03-15 02:21:44 -04:00
2011-03-21 00:16:08 -04:00
2011-03-21 01:10:41 -04:00
2011-03-14 09:15:28 -04:00