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:15:35 -0700 |
| commit | bf0972039ddc483a9cb79edae73076c635876568 (patch) | |
| tree | c86c56c5ca6b5759212f08368e7d3353b33d1b8b /Documentation/cpu-load.txt | |
| parent | 39305a6ac73ca6e8349773d032cdb5336d42196f (diff) | |
| download | linux-stable-bf0972039ddc483a9cb79edae73076c635876568.tar.gz linux-stable-bf0972039ddc483a9cb79edae73076c635876568.tar.bz2 linux-stable-bf0972039ddc483a9cb79edae73076c635876568.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 'Documentation/cpu-load.txt')
0 files changed, 0 insertions, 0 deletions