patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: stable@dpdk.org, ktraynor@redhat.com, lihuisong@huawei.com,
	 haijie1@huawei.com
Subject: Re: [PATCH 20.11] net/hns3: fix traffic management thread safety
Date: Thu, 16 Nov 2023 15:27:41 +0000	[thread overview]
Message-ID: <CAMw=ZnRS1a92C=QKgCc6Sf1BfCzKRrcFhSQFLQbnJLmS_JsMmw@mail.gmail.com> (raw)
In-Reply-To: <20231116123455.36816-1-fengchengwen@huawei.com>

On Thu, 16 Nov 2023 at 12:37, Chengwen Feng <fengchengwen@huawei.com> wrote:
>
> [ upstream commit 69901040975bff8a38edfc47aee727cadc87d356 ]
>
> The driver-related TM (traffic management) info is implemented through
> the linked list. The following threads are involved in the read and
> write of the TM info:
>
> 1. main thread: invokes the rte_tm_xxx() API family to modify or read.
> 2. interrupt thread: will read TM info in reset recover process.
>
> Currently, thread safety protection of TM info is implemented only in
> the following operations:
> 1. some of the rte_tm_xxx() API's implementation.
> 2. reset recover process.
>
> Thread safety risks may exist in other scenarios, so fix by make sure
> all the rte_tm_xxx() API's implementations protected by hw.lock.
>
> Fixes: c09c7847d892 ("net/hns3: support traffic management")
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
> ---
>  drivers/net/hns3/hns3_tm.c | 173 ++++++++++++++++++++++++++++++++-----
>  1 file changed, 150 insertions(+), 23 deletions(-)
>

This patch doesn't apply on 20.11, did you mean to target it at 21.11 or 22.11?

  reply	other threads:[~2023-11-16 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 12:34 Chengwen Feng
2023-11-16 15:27 ` Luca Boccassi [this message]
2023-11-17  1:02   ` fengchengwen
2023-11-23 10:49 ` Kevin Traynor

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='CAMw=ZnRS1a92C=QKgCc6Sf1BfCzKRrcFhSQFLQbnJLmS_JsMmw@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=fengchengwen@huawei.com \
    --cc=haijie1@huawei.com \
    --cc=ktraynor@redhat.com \
    --cc=lihuisong@huawei.com \
    --cc=stable@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).