backing-dev: bdi sb prune should be in the unregister path, not destroy
authorJens Axboe <jens.axboe@oracle.com>
Tue, 3 Nov 2009 19:18:44 +0000 (20:18 +0100)
committerJens Axboe <jens.axboe@oracle.com>
Tue, 3 Nov 2009 19:18:44 +0000 (20:18 +0100)
commit8c4db3355b0fcc9ad77431f15b955efa0645b5d0
tree59182683545e9ca548d0e17e52d6326bb24b44cf
parent5f04eeb8a76521dec371ceb05e8263889a8af2bc
backing-dev: bdi sb prune should be in the unregister path, not destroy

Commit 592b09a42fc3ae6737a0f3ecf4fee42ecd0296f8 was different from
the tested path, in that it moved the bdi super_block prune from
unregister to destroy context. This doesn't fully fix the sync hang
bug on unexpected device removal, as need to prune the bdi cache
pointer before killing flusher thread.

Tested-by: Artur Skawina <art.08.09@gmail.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
mm/backing-dev.c