DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [PATCH] eal: fix thread race in control thread creation
Date: Wed, 1 Mar 2023 09:19:21 +0100	[thread overview]
Message-ID: <CAJFAV8y=KX9yhXmiBU1HCOYsBYhAVdWDyunDZsVjg5WNj9etPQ@mail.gmail.com> (raw)
In-Reply-To: <1677518230-1194-1-git-send-email-roretzla@linux.microsoft.com>

On Mon, Feb 27, 2023 at 6:17 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> When ctrl_thread_init transitions params->ctrl_thread_status from
> CTRL_THREAD_LAUNCHING the creating thread and new thread may run
> concurrently leading to unsynchronized access to params.
>
> This permits races for both the failure and success paths after
> ctrl_thread_status is stored.
>   * params->ret may be loaded in ctrl_thread_init failure path
>   * params->arg may be loaded in ctrl_thread_start or
>     control_thread_start when calling start_routine.
>
> for ctrl_thread_init remove the params->ret load and just return 1 since

For*

> it is only interpreted as a indicator of success / failure of
> ctrl_thread_init.
>
> for {ctrl,control}_thread_start store param->arg in stack allocated

For*

> storage prior to calling ctrl_thread_init and use the copy when calling
> start_routine.
>
> for control_thread_start if ctrl_thread_init fails just return 0 instead

For*



> of loading params->ret, since the value returned is unused when
> ctrl_thread_status is set to CTRL_THREAD_ERROR when ctrl_thread_init
> fails.
>
> Fixes: 878b7468eacb ("eal: add platform agnostic control thread API")
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>

Reviewed-by: David Marchand <david.marchand@redhat.com>

Thanks Tyler.

-- 
David Marchand


  reply	other threads:[~2023-03-01  8:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 17:17 Tyler Retzlaff
2023-03-01  8:19 ` David Marchand [this message]
2023-03-01 21:09 ` [PATCH v2] " Tyler Retzlaff
2023-03-02  1:30   ` Honnappa Nagarahalli
2023-03-02  1:45     ` Tyler Retzlaff
2023-03-02  4:08       ` Honnappa Nagarahalli
2023-03-07 13:53         ` David Marchand
2023-03-07 17:54           ` Tyler Retzlaff
2023-03-09  9:01   ` David Marchand

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='CAJFAV8y=KX9yhXmiBU1HCOYsBYhAVdWDyunDZsVjg5WNj9etPQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=roretzla@linux.microsoft.com \
    --cc=thomas@monjalon.net \
    /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).