From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D2DBFA0A0C; Wed, 4 Aug 2021 18:55:47 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BD2FF4124B; Wed, 4 Aug 2021 18:55:47 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 6F6164118D for ; Wed, 4 Aug 2021 18:55:46 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 5D701A0C40; Wed, 4 Aug 2021 18:55:46 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Wed, 04 Aug 2021 16:55:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 21.08 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dg573847474@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 774] Potential deadlock error due to the unrelased lock X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D774 Bug ID: 774 Summary: Potential deadlock error due to the unrelased lock Product: DPDK Version: 21.08 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: dg573847474@gmail.com Target Milestone: --- source: dpdk/drivers/net/mlx5/mlx5_txpp.c Hi, developers, thank you for your checking. The lock &sh->txpp.mutex may be not released correctly the method returns at the branch !sh->txpp.refcnt || --sh->txpp.refcnt satisfies. The fix is to insert pthread_mutex_lock(&sh->txpp.mutex); before returning. void mlx5_txpp_stop(struct rte_eth_dev *dev) { struct mlx5_priv *priv =3D dev->data->dev_private; struct mlx5_dev_ctx_shared *sh =3D priv->sh; int ret; if (!priv->txpp_en) { return; } priv->txpp_en =3D 0; ret =3D pthread_mutex_lock(&sh->txpp.mutex); // the lock MLX5_ASSERT(!ret); RTE_SET_USED(ret); MLX5_ASSERT(sh->txpp.refcnt); if (!sh->txpp.refcnt || --sh->txpp.refcnt) return; // return without releasing mlx5_txpp_destroy(sh); ret =3D pthread_mutex_unlock(&sh->txpp.mutex); MLX5_ASSERT(!ret); RTE_SET_USED(ret); } --=20 You are receiving this mail because: You are the assignee for the bug.=