Btrfs: avoid risk of a deadlock in btrfs_handle_error
authorStefan Behrens <sbehrens@giantdisaster.de>
Mon, 5 Nov 2012 16:11:06 +0000 (17:11 +0100)
committerJosef Bacik <jbacik@fusionio.com>
Wed, 12 Dec 2012 22:15:36 +0000 (17:15 -0500)
commit1acd6831d98779c88cd57f0a5826d6df0b09f3fa
treec5e7773bcf197766a126b5d2723e058eb5b45bc6
parentaa1b8cd409f05e1489ec77ff219eff6ed4b801b8
Btrfs: avoid risk of a deadlock in btrfs_handle_error

Remove the attempt to cancel a running scrub or device replace
operation in btrfs_handle_error() because it adds the risk of
a deadlock. The only penalty of not canceling the operation is
that some I/O remains active until the procedure completes.
This is basically the same thing that happens to other tasks
that are running in user mode context, they are not affected
or stopped in btrfs_handle_error(), these tasks just need to
handle write errors correctly.

Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/super.c