From: Kevin Traynor <ktraynor@redhat.com>
To: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>, stable@dpdk.org
Cc: harry.van.haaren@intel.com
Subject: Re: [PATCH 21.11] service: fix early move to inactive status
Date: Tue, 1 Nov 2022 14:53:19 +0000 [thread overview]
Message-ID: <1b949edd-6eed-e5f6-1fb1-5284a8d555e6@redhat.com> (raw)
In-Reply-To: <20221026201442.3062175-1-erik.g.carrillo@intel.com>
On 26/10/2022 21:14, Erik Gabriel Carrillo wrote:
> [ upstream commit 329280c53e6d09002b67e4d052fe27a952bd19cf ]
>
> Assume thread T2 is a service lcore that is in the middle of executing
> a service function. Also, assume thread T1 concurrently calls
> rte_service_lcore_stop(), which will set the "service_active_on_lcore"
> state to false. If thread T1 then calls rte_service_may_be_active(),
> it can return zero even though T2 is still running the service function.
> If T1 then proceeds to free data being used by T2, a crash can ensue.
>
> Move the logic that clears the "service_active_on_lcore" state from the
> rte_service_lcore_stop() function to the service_runner_func() to
> ensure that we:
> - don't let the "service_active_on_lcore" state linger as 1
> - don't clear the state early
>
> Fixes: 6550113be62d ("service: fix lingering active status")
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> ---
> lib/eal/common/rte_service.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
Thanks for rebasing, applied.
prev parent reply other threads:[~2022-11-01 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 20:14 Erik Gabriel Carrillo
2022-11-01 14:53 ` Kevin Traynor [this message]
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=1b949edd-6eed-e5f6-1fb1-5284a8d555e6@redhat.com \
--to=ktraynor@redhat.com \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.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).