DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v1 1/1] memory: handle invalid socket ID's when allocating
Date: Fri, 27 Jun 2025 12:46:31 +0200	[thread overview]
Message-ID: <3865806.FMhQkTaH9n@thomas> (raw)
In-Reply-To: <3956282.MyG8hOvIyE@thomas>

27/06/2025 12:44, Thomas Monjalon:
> 20/06/2025 15:37, Bruce Richardson:
> > On Fri, Jun 20, 2025 at 02:30:23PM +0100, Anatoly Burakov wrote:
> > > This issue was reported by static analysis. It is a false positive,
> > > because both `rte_socket_count` and `rte_socket_id_by_idx` only report
> > > information about physical sockets, and these specific calls are made
> > > during EAL initialization, so no other sockets (i.e. external) could have
> > > been available, so it is pretty much impossible to get invalid return here.
> > > 
> > > Still, to avoid future false positives, we can fix it here.
> > > 
> > > Coverity issue: 470131
> > > 
> > > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Applied, thanks?

Sorry for this typo, it was not supposed to be a question mark.
Yes you absolutely deserve some thanks for your continuous maintenance
of the DPDK memory subsystem. Thank you Anatoly :)




  reply	other threads:[~2025-06-27 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 13:30 Anatoly Burakov
2025-06-20 13:37 ` Bruce Richardson
2025-06-27 10:44   ` Thomas Monjalon
2025-06-27 10:46     ` Thomas Monjalon [this message]
2025-06-27 14:53       ` Burakov, Anatoly

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=3865806.FMhQkTaH9n@thomas \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).