patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Rui Ferreira (A)" <rui.ferreira1@h-partners.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"David Marchand" <david.marchand@redhat.com>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: RE: [PATCH v2] fix eal/linux: unregister alarm callback before free
Date: Thu, 29 May 2025 08:39:30 +0000	[thread overview]
Message-ID: <dcbff1c1ee8c48598294306fe80167ef@h-partners.com> (raw)
In-Reply-To: <1969712.QZUTf85G27@thomas>

Hi. I'll try to have a look in the next couple days. 

BR

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, May 27, 2025 3:54 PM
> To: Rui Ferreira (A) <rui.ferreira1@h-partners.com>
> Cc: dev@dpdk.org; stable@dpdk.org; David Marchand
> <david.marchand@redhat.com>; Konstantin Ananyev
> <konstantin.ananyev@huawei.com>
> Subject: Re: [PATCH v2] fix eal/linux: unregister alarm callback before free
> 
> Hello,
> 
> Did you see the comment from David about fixing for Windows and FreeBSD
> at the same time?
> I think you just need to apply the same logic in 3 different places.
> If you cannot test all, that's OK to submit the changes without full coverage
> testing.
> 
> Thank you
> 
> 
> 22/05/2025 17:59, Rui Ferreira:
> > 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. The interrupt thread can dereference the ptr after free (from
> > the alarm callback). free is called when the main thread cleans up.
> >
> > 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.
> >
> > rte_intr_callback_unregister_sync may (optionally) use traces so the
> > alarm cleanup must happen before eal_trace_fini to avoid accessing
> > freed memory.
> >
> > Bugzilla ID: 1683
> >
> > Signed-off-by: Rui Ferreira <rui.ferreira1@h-partners.com>
> > ---
> >  .mailmap                  | 1 +
> >  lib/eal/linux/eal.c       | 3 ++-
> >  lib/eal/linux/eal_alarm.c | 9 ++++++++-
> >  3 files changed, 11 insertions(+), 2 deletions(-)
> 
> 


  reply	other threads:[~2025-05-29  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250520160150.50401-1-rui.ferreira1@h-partners.com>
2025-05-22 15:59 ` Rui Ferreira
2025-05-27 10:22   ` Konstantin Ananyev
2025-05-27 14:53   ` Thomas Monjalon
2025-05-29  8:39     ` Rui Ferreira (A) [this message]
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

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=dcbff1c1ee8c48598294306fe80167ef@h-partners.com \
    --to=rui.ferreira1@h-partners.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=stable@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).