[PATCH v1 1/1] memory: handle invalid socket ID's when allocating

[Burakov, Anatoly]

On 6/27/2025 12:46 PM, Thomas Monjalon wrote:
> 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 at intel.com>
>>> Acked-by: Bruce Richardson <bruce.richardson at 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 :)
> 

Thanks for the kind words, and yes, I did infer it was a typo :)
-- 
Thanks,
Anatoly