All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiangyiwen <jiangyiwen@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
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: Thu, 8 Aug 2019 09:59:18 +0800	[thread overview]
Message-ID: <5D4B81F6.7010002@huawei.com> (raw)
In-Reply-To: <20190807121037.GC1557@ziepe.ca>

Hi Jason,

On 2019/8/7 20:10, Jason Gunthorpe wrote:
> 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
>
Thank you for your reply, and can you tell me the commit id?
I use the kernel version is Linux4.19.36.

Thanks,
Yiwen.


WARNING: multiple messages have this Message-ID (diff)
From: Jiangyiwen <jiangyiwen@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
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: Thu, 08 Aug 2019 01:59:18 +0000	[thread overview]
Message-ID: <5D4B81F6.7010002@huawei.com> (raw)
In-Reply-To: <20190807121037.GC1557@ziepe.ca>

Hi Jason,

On 2019/8/7 20:10, Jason Gunthorpe wrote:
> 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
>
Thank you for your reply, and can you tell me the commit id?
I use the kernel version is Linux4.19.36.

Thanks,
Yiwen.

  reply	other threads:[~2019-08-08  1:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  2:21 [bug report] rdma: rtnl_lock deadlock? Jiangyiwen
2019-08-07  2:21 ` Jiangyiwen
2019-08-07 12:10 ` Jason Gunthorpe
2019-08-07 12:10   ` Jason Gunthorpe
2019-08-08  1:59   ` Jiangyiwen [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=5D4B81F6.7010002@huawei.com \
    --to=jiangyiwen@huawei.com \
    --cc=bvanassche@acm.org \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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 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.