[PATCH v1 1/1] memory: handle invalid socket ID's when allocating
Thomas Monjalon
thomas at monjalon.net
Fri Jun 27 12:44:13 CEST 2025
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 at intel.com>
> Acked-by: Bruce Richardson <bruce.richardson at intel.com>
Applied, thanks?
More information about the dev
mailing list