From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: YE Chengfeng <cyeaa@connect.ust.hk>,
"asomalap@amd.com" <asomalap@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix potential unreleased lock problem
Date: Mon, 30 Aug 2021 07:59:57 +0000 [thread overview]
Message-ID: <DM6PR12MB37532D44CBDB7C2D45180450DFCB9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <TYCP286MB1188D0B8338841026E6FD9C38AC79@TYCP286MB1188.JPNP286.PROD.OUTLOOK.COM>
Hi, Chengfeng
Thank you for the fix, we can adopt this (ie Upstream ML is not "wrong place" 😊)
I have some minor comment about:
- the problem should be described in past tense (should b e"sh->txpp.mutex WAS not correctly")
- headline should be more specific, like "fix mutex unlock in txpp cleanup")
- "Fixes:" tag should be present
- Cc: stable@dpdk.org should be present
Could you, please, update and send v3 ?
With best regards,
Slava
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of YE Chengfeng
> Sent: Thursday, August 26, 2021 22:06
> To: asomalap@amd.com
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] 回复: [PATCH v2] net/mlx5: fix potential unreleased lock
> problem
>
> It seems that I send this patch to a wrong place, please just ignore it.
>
> Thanks,
> Chengfeng
> ________________________________
> 发件人: YE Chengfeng <cyeaa@connect.ust.hk>
> 发送时间: 2021年8月27日 2:56
> 收件人: asomalap@amd.com <asomalap@amd.com>
> 抄送: dev@dpdk.org <dev@dpdk.org>; YE Chengfeng
> <cyeaa@connect.ust.hk>
> 主题: [PATCH v2] net/mlx5: fix potential unreleased lock problem
>
> The lock sh->txpp.mutex isn't correctly released if the function return in
> these two branches, which may lead to deadlock if the lock is acquired again.
>
> Cc: cyeaa@connect.ust.hk
> Bugzilla ID: 774
>
> Signed-off-by: Chengfeng Ye <cyeaa@connect.ust.hk>
> ---
> drivers/net/mlx5/mlx5_txpp.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_txpp.c b/drivers/net/mlx5/mlx5_txpp.c
> index 4f6da9f2d1..0ece788a84 100644
> --- a/drivers/net/mlx5/mlx5_txpp.c
> +++ b/drivers/net/mlx5/mlx5_txpp.c
> @@ -961,8 +961,12 @@ mlx5_txpp_stop(struct rte_eth_dev *dev)
> MLX5_ASSERT(!ret);
> RTE_SET_USED(ret);
> MLX5_ASSERT(sh->txpp.refcnt);
> - if (!sh->txpp.refcnt || --sh->txpp.refcnt)
> + if (!sh->txpp.refcnt || --sh->txpp.refcnt) {
> + ret = pthread_mutex_unlock(&sh->txpp.mutex);
> + MLX5_ASSERT(!ret);
> + RTE_SET_USED(ret);
> return;
> + }
> /* No references any more, do actual destroy. */
> mlx5_txpp_destroy(sh);
> ret = pthread_mutex_unlock(&sh->txpp.mutex);
> --
> 2.17.1
next prev parent reply other threads:[~2021-08-30 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 18:56 Chengfeng Ye
2021-08-26 19:06 ` [dpdk-dev] 回复: " YE Chengfeng
2021-08-30 7:59 ` Slava Ovsiienko [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 18:55 [dpdk-dev] " Chengfeng Ye
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=DM6PR12MB37532D44CBDB7C2D45180450DFCB9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=asomalap@amd.com \
--cc=cyeaa@connect.ust.hk \
--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).