public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	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: Tue, 20 Aug 2024 14:50:05 +0800	[thread overview]
Message-ID: <d61bcb00-301c-400e-9738-b4ec5463f1b9@linux.dev> (raw)
In-Reply-To: <ZsP0ae1Y5ztsqFj1@xsang-OptiPlex-9020>


在 2024/8/20 9:42, Oliver Sang 写道:
> hi, Zhu Yanjun,
>
> On Sun, Aug 18, 2024 at 02:24:52PM +0800, Oliver Sang wrote:
>> hi, Yanjun.Zhu,
>>
>> On Sat, Aug 17, 2024 at 04:46:23PM +0800, Zhu Yanjun wrote:
>>> 在 2024/8/17 1:10, Bart Van Assche 写道:
>>>> On 8/16/24 5:49 AM, Zhu Yanjun wrote:
>>>>> Hi, kernel test robot
>>>>>
>>>>> Please help to make tests with the following commits.
>>>>>
>>>>> Please let us know the result.
>>>> I don't think that the kernel test robot understands the above request.
>>> Got it. I do not know how to let test robot make tests with this patch.^_^
>> we can test the patch for you. just cannot test quickly due to resource
>> constraint. will let you know the results in one or two days. thanks
> the WARNING is random in our tests. for aee2424246, it shows up 6 times in 20
> runs as below table.
>
> the "e0cc1e2cd74a66b5252ea674a26" is just your fix patch.
>
> we run it to 100 times, and the issue doesn't show.
>
> Tested-by: kernel test robot <oliver.sang@intel.com>

Thanks a lot for your tests. I will send out the latest patch very soon.

Zhu Yanjun

>
> a1babdb5b615751e aee2424246f9f1dadc33faa7899 e0cc1e2cd74a66b5252ea674a26
> ---------------- --------------------------- ---------------------------
>         fail:runs  %reproduction    fail:runs  %reproduction    fail:runs
>             |             |             |             |             |
>             :20          30%           6:20           0%            :100   dmesg.RIP:check_flush_dependency
>             :20          30%           6:20           0%            :100   dmesg.WARNING:at_kernel/workqueue.c:#check_flush_dependency
>
>
>>> Follow your advice, I have sent out a patch to rdma maillist. Please review.
>>>
>>> Best Regards,
>>>
>>> Zhu Yanjun
>>>
>>>> Thanks,
>>>>
>>>> Bart.
>>> -- 
>>> Best Regards,
>>> Yanjun.Zhu
>>>
-- 
Best Regards,
Yanjun.Zhu


  reply	other threads:[~2024-08-20  6:50 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 [this message]
2024-08-16 17:09     ` Bart Van Assche
2024-08-17  6:51       ` Zhu Yanjun

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=d61bcb00-301c-400e-9738-b4ec5463f1b9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox