From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95127C32751 for ; Thu, 8 Aug 2019 01:59:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C4F0217F4 for ; Thu, 8 Aug 2019 01:59:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730459AbfHHB7b (ORCPT ); Wed, 7 Aug 2019 21:59:31 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:4189 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730038AbfHHB7b (ORCPT ); Wed, 7 Aug 2019 21:59:31 -0400 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 7AB4C678FD00CB725A9E; Thu, 8 Aug 2019 09:59:27 +0800 (CST) Received: from [127.0.0.1] (10.133.205.88) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.439.0; Thu, 8 Aug 2019 09:59:18 +0800 Subject: Re: [bug report] rdma: rtnl_lock deadlock? To: Jason Gunthorpe References: <5D4A3597.5020406@huawei.com> <20190807121037.GC1557@ziepe.ca> CC: , , , , , Xiexiangyou From: Jiangyiwen Message-ID: <5D4B81F6.7010002@huawei.com> Date: Thu, 8 Aug 2019 09:59:18 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20190807121037.GC1557@ziepe.ca> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.133.205.88] X-CFilter-Loop: Reflected Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiangyiwen Date: Thu, 08 Aug 2019 01:59:18 +0000 Subject: Re: [bug report] rdma: rtnl_lock deadlock? Message-Id: <5D4B81F6.7010002@huawei.com> List-Id: References: <5D4A3597.5020406@huawei.com> <20190807121037.GC1557@ziepe.ca> In-Reply-To: <20190807121037.GC1557@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jason Gunthorpe Cc: bvanassche@acm.org, dledford@redhat.com, linux-rdma@vger.kernel.org, target-devel@vger.kernel.org, yebiaoxiang@huawei.com, Xiexiangyou 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.