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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 20 Dec 2013 15:49:09 +0000 (07:49 -0800)
commit486d1e163be2d32150a053c7ac3fc853ba6fd998
tree88818a5e4914a70c168f476dae55141aacfc34e1
parent222ae8bfd4c3796335d2aa1aa6a4dbeccb497b00
Btrfs: take ordered root lock when removing ordered operations inode

commit 93858769172c4e3678917810e9d5de360eb991cc upstream.

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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/btrfs/ordered-data.c