From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jiangyiwen <jiangyiwen@huawei.com>
Cc: bvanassche@acm.org, dledford@redhat.com,
linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
yebiaoxiang@huawei.com, Xiexiangyou <xiexiangyou@huawei.com>
Subject: Re: [bug report] rdma: rtnl_lock deadlock?
Date: Wed, 7 Aug 2019 09:10:37 -0300 [thread overview]
Message-ID: <20190807121037.GC1557@ziepe.ca> (raw)
In-Reply-To: <5D4A3597.5020406@huawei.com>
On Wed, Aug 07, 2019 at 10:21:11AM +0800, Jiangyiwen wrote:
> Hello,
>
> I find a scenario may cause deadlock of rtnl_lock as follows:
>
> 1. CPU1 add rtnl_lock and wait kworker finished.
> CPU1 add rtnl_lock before call unregister_netdevice_queue() and
> then wait sport->work(function srpt_refresh_port_work) finished
> in srpt_remove_one().
This is an old kernel, this issue has been fixed
Jason
next prev parent reply other threads:[~2019-08-07 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 2:21 [bug report] rdma: rtnl_lock deadlock? Jiangyiwen
2019-08-07 12:10 ` Jason Gunthorpe [this message]
2019-08-08 1:59 ` Jiangyiwen
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=20190807121037.GC1557@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jiangyiwen@huawei.com \
--cc=linux-rdma@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=xiexiangyou@huawei.com \
--cc=yebiaoxiang@huawei.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;
as well as URLs for NNTP newsgroup(s).