diff options
| author | NeilBrown <neilb@suse.de> | 2014-09-29 22:10:42 (GMT) |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2014-10-14 02:08:28 (GMT) |
| commit | ac05f256691fe427a3e84c19261adb0b67dd73c0 (patch) | |
| tree | 2f7254e7117eac0fc0d974029e5bb5422866a73c /lib/find_next_bit.c | |
| parent | 8b1afc3d6751063d3f0cdefe55719b1cd2f7edcc (diff) | |
| download | linux-ac05f256691fe427a3e84c19261adb0b67dd73c0.tar.xz | |
md: don't start resync thread directly from md thread.
The main 'md' thread is needed for processing writes, so if it blocks
write requests could be delayed.
Starting a new thread requires some GFP_KERNEL allocations and so can
wait for writes to complete. This can deadlock.
So instead, ask a workqueue to start the sync thread.
There is no particular rush for this to happen, so any work queue
will do.
MD_RECOVERY_RUNNING is used to ensure only one thread is started.
Reported-by: BillStuff <billstuff2001@sbcglobal.net>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'lib/find_next_bit.c')
0 files changed, 0 insertions, 0 deletions