summaryrefslogtreecommitdiff
path: root/drivers/md
diff options
context:
space:
mode:
authorOfer Heifetz <oferh@marvell.com>2017-07-24 06:17:40 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-08-07 01:59:40 (GMT)
commitfabc7dffe9e123e5be2456139853a7e12c5adce8 (patch)
tree7acc674eb865238da0844f04b92557e276fd937e /drivers/md
parentd745f0f67b70afafd4d5f300ec422dae26bbd938 (diff)
downloadlinux-fabc7dffe9e123e5be2456139853a7e12c5adce8.tar.xz
md/raid5: add thread_group worker async_tx_issue_pending_all
commit 7e96d559634b73a8158ee99a7abece2eacec2668 upstream. Since thread_group worker and raid5d kthread are not in sync, if worker writes stripe before raid5d then requests will be waiting for issue_pendig. Issue observed when building raid5 with ext4, in some build runs jbd2 would get hung and requests were waiting in the HW engine waiting to be issued. Fix this by adding a call to async_tx_issue_pending_all in the raid5_do_work. Signed-off-by: Ofer Heifetz <oferh@marvell.com> Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/raid5.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 8f117d6..383f19c 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -5843,6 +5843,8 @@ static void raid5_do_work(struct work_struct *work)
pr_debug("%d stripes handled\n", handled);
spin_unlock_irq(&conf->device_lock);
+
+ async_tx_issue_pending_all();
blk_finish_plug(&plug);
pr_debug("--- raid5worker inactive\n");