btrfs: fix locking when we put back a delayed ref that's too new
authorJeff Mahoney <jeffm@suse.com>
Tue, 20 Dec 2016 18:28:28 +0000 (13:28 -0500)
committerDavid Sterba <dsterba@suse.com>
Tue, 3 Jan 2017 14:14:21 +0000 (15:14 +0100)
commitd0280996437081dd12ed1e982ac8aeaa62835ec4
tree9c1e103ecde5541b14903fa7f08630c5ebda84e6
parentaa7c8da35d1905d80e840d075f07d26ec90144b5
btrfs: fix locking when we put back a delayed ref that's too new

In __btrfs_run_delayed_refs, when we put back a delayed ref that's too
new, we have already dropped the lock on locked_ref when we set
->processing = 0.

This patch keeps the lock to cover that assignment.

Fixes: d7df2c796d7 (Btrfs: attach delayed ref updates to delayed ref heads)
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent-tree.c