diff options
author | Jan Kara <jack@suse.cz> | 2014-04-03 14:46:23 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-04-26 17:19:05 -0700 |
commit | 1c23ab6f8860f1d5823868d868314f674333a8b3 (patch) | |
tree | 9953b1d22dc2fed150e59bc9a00fa8fa56017f62 /fs/ext2 | |
parent | 67001f3a0bc4373452a2a3241e4b038bdc796cda (diff) | |
download | kernel-common-1c23ab6f8860f1d5823868d868314f674333a8b3.tar.gz kernel-common-1c23ab6f8860f1d5823868d868314f674333a8b3.tar.bz2 kernel-common-1c23ab6f8860f1d5823868d868314f674333a8b3.zip |
bdi: avoid oops on device removal
commit 5acda9d12dcf1ad0d9a5a2a7c646de3472fa7555 upstream.
After commit 839a8e8660b6 ("writeback: replace custom worker pool
implementation with unbound workqueue") when device is removed while we
are writing to it we crash in bdi_writeback_workfn() ->
set_worker_desc() because bdi->dev is NULL.
This can happen because even though bdi_unregister() cancels all pending
flushing work, nothing really prevents new ones from being queued from
balance_dirty_pages() or other places.
Fix the problem by clearing BDI_registered bit in bdi_unregister() and
checking it before scheduling of any flushing work.
Fixes: 839a8e8660b6777e7fe4e80af1a048aebe2b5977
Reviewed-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Jan Kara <jack@suse.cz>
Cc: Derek Basehore <dbasehore@chromium.org>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext2')
0 files changed, 0 insertions, 0 deletions