| commit | 90290e19820e3323ce6b9c2888eeb68bf29c278b | |
| author | Josef Bacik <josef@redhat.com> | |
| Fri, 2 Dec 2011 20:44:12 +0000 (2 15:44 -0500) | ||
| committer | Chris Mason <chris.mason@oracle.com> | |
| Mon, 16 Jan 2012 20:29:42 +0000 (16 15:29 -0500) | ||
| tree | cdac13a9718d326cdcd9f4b215a5739906a2325a | treesnapshot (tar.gz zip) |
| parent | 3f7de037fb3727b20bc27332cdcf2488b702394c | commitdiff |
Btrfs: protect orphan block rsv with spin_lock
We've been seeing warnings coming out of the orphan commit stuff forever from
ceph. Turns out it's because we're racing with checking if the orphan block
reserve is set, because we clear it outside of the spin_lock. So leave the
normal fastpath checks where they are, but take the spin_lock and _recheck_ to
make sure we haven't had an orphan block rsv added in the meantime. Then clear
the root's orphan block rsv and release the lock. With this patch a user said
the warnings went away and they usually showed up pretty soon after he started
ceph. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
We've been seeing warnings coming out of the orphan commit stuff forever from
ceph. Turns out it's because we're racing with checking if the orphan block
reserve is set, because we clear it outside of the spin_lock. So leave the
normal fastpath checks where they are, but take the spin_lock and _recheck_ to
make sure we haven't had an orphan block rsv added in the meantime. Then clear
the root's orphan block rsv and release the lock. With this patch a user said
the warnings went away and they usually showed up pretty soon after he started
ceph. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
| fs/btrfs/inode.c | diffblobblamehistory |