Btrfs: take ordered root lock when removing ordered operations inode
authorJosef Bacik <jbacik@fusionio.com>
Mon, 28 Oct 2013 13:13:25 +0000 (09:13 -0400)
committerChris Mason <chris.mason@fusionio.com>
Tue, 12 Nov 2013 03:08:10 +0000 (22:08 -0500)
commit93858769172c4e3678917810e9d5de360eb991cc
treef1674e2bd0b7837cc1738dd1a6261adc30c1111a
parentd788a34929a90f70b945c100cfe9efd4d49fb446
Btrfs: take ordered root lock when removing ordered operations inode

A user reported a list corruption warning from btrfs_remove_ordered_extent, it
is because we aren't taking the ordered_root_lock when we remove the inode from
the ordered operations list.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/ordered-data.c