From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: "Rui Ferreira (A)" <rui.ferreira1@h-partners.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] eal/linux: unregister alarm callback before free ptr
Date: Wed, 21 May 2025 11:43:01 +0000 [thread overview]
Message-ID: <462157df1f3742f7abd20ee27067c53b@huawei.com> (raw)
In-Reply-To: <20250520160150.50401-1-rui.ferreira1@h-partners.com>
> Subject: [PATCH] eal/linux: unregister alarm callback before free ptr
>
> This was flagged by Address sanitizer as a use after free. The
> intr_handle ptr is shared between the main thread and the interrupt
> thread, and the interrupt thread can dereference the ptr after free
> is called when the main thread cleans up (from the alarm callback).
>
> The interrupt thread never terminates (eal_intr_thread_main) so
> use rte_intr_callback_unregister_sync during cleanup to
> ensure the callback is removed before freeing the ptr.
>
> To be more defensive clear out the pointer and registration
> variable if we can unregister.
>
> Bugzilla ID: 1683
>
> Signed-off-by: Rui Ferreira <rui.ferreira1@h-partners.com>
> ---
> .mailmap | 1 +
> lib/eal/linux/eal_alarm.c | 9 ++++++++-
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/.mailmap b/.mailmap
> index d8439b79ce..907c5ea967 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -1332,6 +1332,7 @@ Rosen Xu <rosen.xu@altera.com> <rosen.xu@intel.com>
> Roy Franz <roy.franz@cavium.com>
> Roy Pledge <roy.pledge@nxp.com>
> Roy Shterman <roy.shterman@vastdata.com>
> +Rui Ferreira <rui.ferreira1@h-partners.com>
> Ruifeng Wang <ruifeng.wang@arm.com>
> Rushil Gupta <rushilg@google.com>
> Ryan E Hall <ryan.e.hall@intel.com>
> diff --git a/lib/eal/linux/eal_alarm.c b/lib/eal/linux/eal_alarm.c
> index b216a007a3..eb6a21d4f0 100644
> --- a/lib/eal/linux/eal_alarm.c
> +++ b/lib/eal/linux/eal_alarm.c
> @@ -57,7 +57,14 @@ static void eal_alarm_callback(void *arg);
> void
> rte_eal_alarm_cleanup(void)
> {
> - rte_intr_instance_free(intr_handle);
> + /* unregister callback using intr_handle in interrupt thread */
> + int ret = rte_intr_callback_unregister_sync(intr_handle,
> + eal_alarm_callback, (void *)-1);
> + if (ret >= 0) {
> + rte_intr_instance_free(intr_handle);
> + intr_handle = NULL;
> + handler_registered = 0;
> + }
> }
>
> int
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
As a nit: as it is a bug-fix, probably start with 'fix ..' in the subject.
Also "Fixes:" and probably " Cc: stable@dpdk.org" needs to be added.
> 2.35.3
next prev parent reply other threads:[~2025-05-21 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:01 [PATCH] eal/linux: unregister alarm callback before free ptr Rui Ferreira
2025-05-21 8:49 ` David Marchand
2025-05-21 11:43 ` Konstantin Ananyev [this message]
2025-05-22 15:59 ` [PATCH v2] fix eal/linux: unregister alarm callback before free Rui Ferreira
2025-05-27 10:22 ` Konstantin Ananyev
2025-05-27 14:53 ` Thomas Monjalon
2025-05-29 8:39 ` Rui Ferreira (A)
2025-05-30 8:18 ` [PATCH v2 0/2] fix eal: " Rui Ferreira
2025-05-30 8:18 ` [PATCH v2 1/2] fix eal/linux: " Rui Ferreira
2025-05-30 8:18 ` [PATCH v2 2/2] fix eal/freebsd: " Rui Ferreira
2025-06-03 8:29 ` Bruce Richardson
2025-06-09 12:45 ` Thomas Monjalon
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=462157df1f3742f7abd20ee27067c53b@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=dev@dpdk.org \
--cc=rui.ferreira1@h-partners.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.