All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Bart Van Assche <bvanassche@acm.org>,
	kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, Leon Romanovsky <leon@kernel.org>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [linus:master] [RDMA/iwcm] aee2424246: WARNING:at_kernel/workqueue.c:#check_flush_dependency
Date: Sat, 17 Aug 2024 14:51:16 +0800	[thread overview]
Message-ID: <3ca021d4-9cce-4402-8a4e-104df6459bc2@linux.dev> (raw)
In-Reply-To: <d698161b-f9f4-490b-98a5-b51d739d4136@acm.org>


在 2024/8/17 1:09, Bart Van Assche 写道:
> On 8/15/24 10:27 PM, Zhu Yanjun wrote:
>> diff --git a/drivers/infiniband/core/iwcm.c 
>> b/drivers/infiniband/core/iwcm.c
>> index 1a6339f3a63f..7e3a55349e10 100644
>> --- a/drivers/infiniband/core/iwcm.c
>> +++ b/drivers/infiniband/core/iwcm.c
>> @@ -1182,7 +1182,7 @@ static int __init iw_cm_init(void)
>>          if (ret)
>>                  return ret;
>>
>> -       iwcm_wq = alloc_ordered_workqueue("iw_cm_wq", 0);
>> +       iwcm_wq = alloc_ordered_workqueue("iw_cm_wq", WQ_MEM_RECLAIM);
>>          if (!iwcm_wq)
>>                  goto err_alloc;
>
> This change looks good go me. Do you plan to post this as a proper patch?

Hi, Bart

Thanks a lot for your review. I will post the patch ASAP.

Zhu Yanjun


>
> Thanks,
>
> Bart.
>
-- 
Best Regards,
Yanjun.Zhu


      reply	other threads:[~2024-08-17  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  1:07 [linus:master] [RDMA/iwcm] aee2424246: WARNING:at_kernel/workqueue.c:#check_flush_dependency kernel test robot
2024-08-16  4:14 ` Zhu Yanjun
2024-08-16  5:27   ` Zhu Yanjun
2024-08-16 12:49     ` Zhu Yanjun
2024-08-16 17:10       ` Bart Van Assche
2024-08-17  8:46         ` Zhu Yanjun
2024-08-18  6:24           ` Oliver Sang
2024-08-20  1:42             ` Oliver Sang
2024-08-20  6:50               ` Zhu Yanjun
2024-08-16 17:09     ` Bart Van Assche
2024-08-17  6:51       ` Zhu Yanjun [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ca021d4-9cce-4402-8a4e-104df6459bc2@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=bvanassche@acm.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=shinichiro.kawasaki@wdc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.