From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org, david.marchand@redhat.com
Cc: thomas@monjalon.net, Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH v2] eal: fix thread race in control thread creation
Date: Wed, 1 Mar 2023 13:07:06 -0800 [thread overview]
Message-ID: <1677704826-2183-1-git-send-email-roretzla@linux.microsoft.com> (raw)
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
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
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
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>
---
lib/eal/common/eal_common_thread.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/lib/eal/common/eal_common_thread.c b/lib/eal/common/eal_common_thread.c
index edb9d4e..079a385 100644
--- a/lib/eal/common/eal_common_thread.c
+++ b/lib/eal/common/eal_common_thread.c
@@ -256,7 +256,7 @@ static int ctrl_thread_init(void *arg)
if (params->ret != 0) {
__atomic_store_n(¶ms->ctrl_thread_status,
CTRL_THREAD_ERROR, __ATOMIC_RELEASE);
- return params->ret;
+ return 1;
}
__atomic_store_n(¶ms->ctrl_thread_status,
@@ -268,23 +268,25 @@ static int ctrl_thread_init(void *arg)
static void *ctrl_thread_start(void *arg)
{
struct rte_thread_ctrl_params *params = arg;
+ void *start_arg = params->arg;
void *(*start_routine)(void *) = params->u.ctrl_start_routine;
if (ctrl_thread_init(arg) != 0)
return NULL;
- return start_routine(params->arg);
+ return start_routine(start_arg);
}
static uint32_t control_thread_start(void *arg)
{
struct rte_thread_ctrl_params *params = arg;
+ void *start_arg = params->arg;
rte_thread_func start_routine = params->u.control_start_routine;
if (ctrl_thread_init(arg) != 0)
- return params->ret;
+ return 0;
- return start_routine(params->arg);
+ return start_routine(start_arg);
}
int
--
1.8.3.1
next reply other threads:[~2023-03-01 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:07 Tyler Retzlaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 17:17 [PATCH] " Tyler Retzlaff
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=1677704826-2183-1-git-send-email-roretzla@linux.microsoft.com \
--to=roretzla@linux.microsoft.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).