> -Original Message-
> From: Thomas Monjalon
> Subject: Re: [PATCH v4] app/pdump: check lcore is not the maximum core
>
> 08/03/2022 14:47, Mcnamara, John:
> > Thomas, could you include this in RC3 if possible.
>
> I did already yesterday:
> https:
08/03/2022 14:47, Mcnamara, John:
> Thomas, could you include this in RC3 if possible.
I did already yesterday:
https://git.dpdk.org/dpdk/commit/?id=3ee04ebc91
Looks like I forgot to send an email.
Applied, thanks :)
> Subject: [PATCH v4] app/pdump: check lcore is not the maximum core
>
> Check lcore id value is not the maximum core supported.
> Using lcore id without this check might cause out of bound access inside
> the rte_eal_wait_lcore.
>
> Coverity issue: 375841
> Fixes: b2854d5
On Mon, 28 Feb 2022 09:58:56 +
Reshma Pattan wrote:
> Check lcore id value is not the maximum core supported.
> Using lcore id without this check might cause
> out of bound access inside the rte_eal_wait_lcore.
>
> Coverity issue: 375841
> Fixes: b2854d5317e8 ("app/pdump: support multi-core
Check lcore id value is not the maximum core supported.
Using lcore id without this check might cause
out of bound access inside the rte_eal_wait_lcore.
Coverity issue: 375841
Fixes: b2854d5317e8 ("app/pdump: support multi-core capture")
Cc: vipin.vargh...@intel.com
Cc: sta...@dpdk.org
Signed-off
5 matches
Mail list logo