From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
Chengfeng Ye <cyeaa@connect.ust.hk>,
Matan Azrad <matan@nvidia.com>, Tzahi Oved <tzahio@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v6] net/mlx5: fix mutex unlock in txpp cleanup
Date: Tue, 16 Nov 2021 17:01:26 +0000 [thread overview]
Message-ID: <8a70eb46-fe9c-e63e-e5f4-f5a490468e22@intel.com> (raw)
In-Reply-To: <DM6PR12MB3753D36BE32E592AE6F2DA01DF999@DM6PR12MB3753.namprd12.prod.outlook.com>
On 11/16/2021 3:04 PM, Slava Ovsiienko wrote:
>> -----Original Message-----
>> From: Chengfeng Ye <cyeaa@connect.ust.hk>
>> Sent: Tuesday, November 16, 2021 16:49
>> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
>> <viacheslavo@nvidia.com>; Tzahi Oved <tzahio@nvidia.com>;
>> ferruh.yigit@intel.com; Raslan Darawsheh <rasland@nvidia.com>
>> Cc: dev@dpdk.org; Chengfeng Ye <cyeaa@connect.ust.hk>; stable@dpdk.org
>> Subject: [PATCH v6] net/mlx5: fix mutex unlock in txpp cleanup
>>
>> The lock sh->txpp.mutex was not correctly released on one path of cleanup
>> function return, potentially causing the deadlock.
>>
>> Fixes: d133f4cdb7 ("net/mlx5: create clock queue for packet pacing")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Chengfeng Ye <cyeaa@connect.ust.hk>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-16 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 14:49 Chengfeng Ye
2021-11-16 15:04 ` Slava Ovsiienko
2021-11-16 17:01 ` Ferruh Yigit [this message]
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=8a70eb46-fe9c-e63e-e5f4-f5a490468e22@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cyeaa@connect.ust.hk \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=tzahio@nvidia.com \
--cc=viacheslavo@nvidia.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).