From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: Bart Van Assche <bvanassche@acm.org>,
Yi Zhang <yi.zhang@redhat.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>
Subject: Re: [bug report] WARNING: possible circular locking at: rdma_destroy_id+0x17/0x20 [rdma_cm] triggered by blktests nvmeof-mp/002
Date: Wed, 25 May 2022 03:40:33 +0000 [thread overview]
Message-ID: <bdf3dd84-be25-d50c-5c8f-39dc652f1140@fujitsu.com> (raw)
In-Reply-To: <bc4ae9f0-3028-3f27-157a-44a00632c214@acm.org>
On 2022/2/28 7:21, Bart Van Assche wrote:
> On 12/3/21 19:04, Yi Zhang wrote:
>> Below WARNING triggered by blktests nvmeof-mp/002, it can be
>> reproduced with the latest 5.16.0-rc3 and also exists on 5.12, pls
>> check it.
>>
>> # use_siw=1 ./check nvmeof-mp/002
>
> I can reproduce this issue with kernel v5.17.0-rc2.
>
> Bart.
Hi Bart and Yi
Could you reproduce it on v5.18.0? I cannot reproduce it on v5.18.0.
Is there a fix patch has been merged into v5.18.0?
Best Regards,
Xiao Yang
next prev parent reply other threads:[~2022-05-25 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 3:04 [bug report] WARNING: possible circular locking at: rdma_destroy_id+0x17/0x20 [rdma_cm] triggered by blktests nvmeof-mp/002 Yi Zhang
2022-02-27 23:21 ` Bart Van Assche
2022-05-25 3:40 ` yangx.jy [this message]
2022-05-25 11:01 ` Sagi Grimberg
2022-05-25 18:50 ` Bart Van Assche
2022-05-27 12:52 ` Jason Gunthorpe
2022-05-28 19:00 ` Bart Van Assche
2022-05-31 12:35 ` Jason Gunthorpe
2022-05-31 17:55 ` Bart Van Assche
2022-06-01 12:45 ` Jason Gunthorpe
2022-06-01 16:26 ` Bart Van Assche
2022-06-01 17:30 ` Jason Gunthorpe
2022-06-03 5:13 ` Bart Van Assche
2022-06-06 16:21 ` Jason Gunthorpe
2022-08-23 7:29 ` yangx.jy
2022-08-25 5:59 ` yangx.jy
2022-08-25 6:26 ` Guoqing Jiang
2022-08-26 10:03 ` yangx.jy
2022-08-26 11:32 ` Guoqing Jiang
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=bdf3dd84-be25-d50c-5c8f-39dc652f1140@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=bvanassche@acm.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yi.zhang@redhat.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