tree 9e2b61f449524e988dacb04a770b87a2e3fddc23
parent 514ac8ad8793a097c0c9d89202c642479d6dfa34
author Chris Mason <clm@fb.com> 1389317280 -0800
committer Chris Mason <clm@fb.com> 1391007990 -0800

Btrfs: setup inode location during btrfs_init_inode_locked

We have a race during inode init because the BTRFS_I(inode)->location is setup
after the inode hash table lock is dropped.  btrfs_find_actor uses the location
field, so our search might not find an existing inode in the hash table if we
race with the inode init code.

This commit changes things to setup the location field sooner.  Also the find actor now
uses only the location objectid to match inodes.  For inode hashing, we just
need a unique and stable test, it doesn't have to reflect the inode numbers we
show to userland.

Signed-off-by: Chris Mason <clm@fb.com>
CC: stable@vger.kernel.org