From: huangdengdui <huangdengdui@huawei.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <stephen@networkplumber.org>,
<lihuisong@huawei.com>, <fengchengwen@huawei.com>,
<liuyonglong@huawei.com>
Subject: Re: [PATCH 1/3] net/hns3: fix inconsistent lock
Date: Fri, 22 Aug 2025 12:00:28 +0800 [thread overview]
Message-ID: <cbebdb96-b25b-4811-bf56-a7772ba9c61e@huawei.com> (raw)
In-Reply-To: <CAJFAV8wKF6vyvTeyjVriOaPo40NrT_sVQ=PoQe+UBrGagVgC9Q@mail.gmail.com>
On 2025/8/21 20:24, David Marchand wrote:
> Hello,
>
> On Wed, Aug 13, 2025 at 9:33 AM Dengdui Huang <huangdengdui@huawei.com> wrote:
>>
>> The hns3 driver supports configuring RSS through both ops API and
>> rte_flow API. The ops API uses spink lock, while the rte_flow API uses
>> pthread mutex lock. When concurrent calls occur, issues may arise.
>> This patch replaces the lock in the flow API with spink lock.
>>
>> Fixes: 1bdcca8006e4 ("net/hns3: fix flow director lock")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
>> ---
>> drivers/net/hns3/hns3_ethdev.h | 1 -
>> drivers/net/hns3/hns3_fdir.c | 13 --------
>> drivers/net/hns3/hns3_flow.c | 57 +++++++++++++---------------------
>> 3 files changed, 22 insertions(+), 49 deletions(-)
>
> With this change, is it possible to enable the lock annotations check?
>
This is fine. I will enable it in the next version.
> I mean:
> $ git diff
> diff --git a/drivers/net/hns3/meson.build b/drivers/net/hns3/meson.build
> index 53a9dd6f39..36ce93ccde 100644
> --- a/drivers/net/hns3/meson.build
> +++ b/drivers/net/hns3/meson.build
> @@ -35,8 +35,6 @@ sources = files(
>
> require_iova_in_mbuf = false
>
> -annotate_locks = false
> -
> deps += ['hash']
>
> cflags += no_wvla_cflag
>
>
>
>
next prev parent reply other threads:[~2025-08-22 4:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 7:33 [PATCH 0/3] net/hns3: bugfix for hns3 Dengdui Huang
2025-08-13 7:33 ` [PATCH 1/3] net/hns3: fix inconsistent lock Dengdui Huang
2025-08-13 21:06 ` Stephen Hemminger
2025-08-21 12:20 ` huangdengdui
2025-08-21 12:24 ` David Marchand
2025-08-22 4:00 ` huangdengdui [this message]
2025-08-13 7:33 ` [PATCH 2/3] net/hns3: fix unrelease VLAN resource when init fail Dengdui Huang
2025-08-13 14:51 ` Stephen Hemminger
2025-08-21 12:16 ` huangdengdui
2025-08-13 7:33 ` [PATCH 3/3] net/hns3: fix overwrite mbuf in vector path Dengdui Huang
2025-08-22 6:04 ` [PATCH v2 0/4] net/hns3: bugfix for hns3 Dengdui Huang
2025-08-22 6:04 ` [PATCH v2 1/4] net/hns3: fix inconsistent lock Dengdui Huang
2025-08-22 6:04 ` [PATCH v2 2/4] net/hns3: enable lock annotations check Dengdui Huang
2025-08-22 6:04 ` [PATCH v2 3/4] net/hns3: fix unrelease VLAN resource when init fail Dengdui Huang
2025-08-22 6:04 ` [PATCH v2 4/4] net/hns3: fix overwrite mbuf in vector path Dengdui Huang
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=cbebdb96-b25b-4811-bf56-a7772ba9c61e@huawei.com \
--to=huangdengdui@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.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).