From: Sagi Grimberg Date: Tue, 15 Aug 2017 19:20:37 +0000 (+0300) Subject: cm: Don't allocate ib_cm workqueue with WQ_MEM_RECLAIM X-Git-Tag: v4.14-rc2~9^2~139^2~17 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=cb93e597779e565dfeda34aede83c2565ddadc97;p=platform%2Fkernel%2Flinux-exynos.git cm: Don't allocate ib_cm workqueue with WQ_MEM_RECLAIM create_workqueue always creates the workqueue with WQ_MEM_RECLAIM and silences a flush dependency warn for WQ_LEGACY. Instead, we want to keep the warn in case the allocator tries to flush the cm workqueue because its very likely that cm work execution will yield memory allocations (for example cm connection requests). Reported-by: Steve Wise Reviewed-by: Steve Wise Reviewed-by: Leon Romanovsky Signed-off-by: Sagi Grimberg Signed-off-by: Doug Ledford --- diff --git a/drivers/infiniband/core/cm.c b/drivers/infiniband/core/cm.c index 2b4d613..838e350 100644 --- a/drivers/infiniband/core/cm.c +++ b/drivers/infiniband/core/cm.c @@ -4201,7 +4201,7 @@ static int __init ib_cm_init(void) goto error1; } - cm.wq = create_workqueue("ib_cm"); + cm.wq = alloc_workqueue("ib_cm", 0, 1); if (!cm.wq) { ret = -ENOMEM; goto error2;