DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 774] Potential deadlock error due to the unrelased lock
Date: Wed, 04 Aug 2021 16:55:46 +0000	[thread overview]
Message-ID: <bug-774-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=774

            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 = dev->data->dev_private;
        struct mlx5_dev_ctx_shared *sh = priv->sh;
        int ret;

        if (!priv->txpp_en) {
                return;
        }
        priv->txpp_en = 0;
        ret = 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 = pthread_mutex_unlock(&sh->txpp.mutex);
        MLX5_ASSERT(!ret);
        RTE_SET_USED(ret);
}

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-08-04 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-774-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).