From: Rui Ferreira <rui.ferreira1@h-partners.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: [PATCH v2 0/2] fix eal: unregister alarm callback before free
Date: Fri, 30 May 2025 09:18:42 +0100 [thread overview]
Message-ID: <20250530081845.64297-1-rui.ferreira1@h-partners.com> (raw)
In-Reply-To: <dcbff1c1ee8c48598294306fe80167ef@h-partners.com>
This was flagged by Address sanitizer as a use after free in Linux. A
pointer is freed in the main thread but used by a callback in another thread.
It can be reliably reproduced in Linux with ASAN but I could not trigger the
same issue in FreeBSD.
I've included nearly identical patches for Linux and FreeBSD. I did not
include any changes for Windows since the same issue does not seem to apply
there (thread is actually cancelled, no shared ptr).
Bugzilla ID: 1683
Rui Ferreira (2):
fix eal/linux: unregister alarm callback before free
fix eal/freebsd: unregister alarm callback before free
.mailmap | 1 +
lib/eal/freebsd/eal.c | 3 ++-
lib/eal/freebsd/eal_alarm.c | 8 +++++++-
lib/eal/linux/eal.c | 3 ++-
lib/eal/linux/eal_alarm.c | 9 ++++++++-
5 files changed, 20 insertions(+), 4 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2025-05-30 8:19 UTC|newest]
Thread overview: 10+ 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
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 ` Rui Ferreira [this message]
2025-05-30 8:18 ` [PATCH v2 1/2] " Rui Ferreira
2025-05-30 8:18 ` [PATCH v2 2/2] fix eal/freebsd: " Rui Ferreira
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=20250530081845.64297-1-rui.ferreira1@h-partners.com \
--to=rui.ferreira1@h-partners.com \
--cc=dev@dpdk.org \
--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).