patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>,
	"christian.ehrhardt@canonical.com"
	<christian.ehrhardt@canonical.com>,
	"Chen,  LingliX" <linglix.chen@intel.com>,
	"Jiang, YuX" <yux.jiang@intel.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v4] telemetry: fix race in telemetry control thread creation
Date: Tue, 13 Jul 2021 13:31:38 +0000	[thread overview]
Message-ID: <MN2PR11MB3821C9C53C99C4B528808B87E6149@MN2PR11MB3821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210713064137.12488-1-alvinx.zhang@intel.com>

Hi Alvin,

>-----Original Message-----
>From: Zhang, AlvinX <alvinx.zhang@intel.com>
>Sent: Tuesday 13 July 2021 07:42
>To: christian.ehrhardt@canonical.com; Chen, LingliX <linglix.chen@intel.com>;
>Jiang, YuX <yux.jiang@intel.com>; Power, Ciara <ciara.power@intel.com>; Van
>Haaren, Harry <harry.van.haaren@intel.com>
>Cc: Zhang, AlvinX <alvinx.zhang@intel.com>; stable@dpdk.org
>Subject: [PATCH v4] telemetry: fix race in telemetry control thread creation
>
>Before the caller returns from function "rte_ctrl_thread_create", the newly
>created thread may have ran, and because the thread control flag was not set
>before, the new thread may exit soon.
>This is not what the developer expected.
>
>This patch puts the setting thread control flag to the place that before creating
>new thread.
>
>Reported-at: https://bugs.dpdk.org/show_bug.cgi?id=731
>Fixes: 8877ac688b52 ("telemetry: introduce infrastructure")
>Cc: stable@dpdk.org
>
>Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
>---
>
<snip>

Thanks for this, I guess it is targeted towards both 18.11 and 19.11 stable releases?
This file was removed in 20.11 so won't be needed there.

Acked-by: Ciara Power <ciara.power@intel.com>



  reply	other threads:[~2021-07-13 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13  6:41 Alvin Zhang
2021-07-13 13:31 ` Power, Ciara [this message]
2021-07-13 13:44   ` 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=MN2PR11MB3821C9C53C99C4B528808B87E6149@MN2PR11MB3821.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=alvinx.zhang@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=harry.van.haaren@intel.com \
    --cc=linglix.chen@intel.com \
    --cc=stable@dpdk.org \
    --cc=yux.jiang@intel.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).