[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-07-21 Thread Thomas Monjalon
2016-07-21 12:01, Mrozowicz, SlawomirX: > Hi Thomas, > > As I understand Sergio suggested to come back to the solution similar to v1. > Could you comment or better take decision which solution should be applied, > please. > > Best Regards, > S?awomir > > > >-Original Message- > >From:

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-07-21 Thread Mrozowicz, SlawomirX
6 1:29 PM >To: Thomas Monjalon >Cc: Mrozowicz, SlawomirX ; >dev at dpdk.org; david.marchand at 6wind.com >Subject: Re: [dpdk-dev] [PATCH v5] eal: out-of-bounds write > >On 20/06/2016 11:09, Thomas Monjalon wrote: >> 2016-06-20 10:38, Sergio Gonzalez Monroy: >>>

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-06-20 Thread Sergio Gonzalez Monroy
On 20/06/2016 11:09, Thomas Monjalon wrote: > 2016-06-20 10:38, Sergio Gonzalez Monroy: >> On 20/06/2016 10:14, Thomas Monjalon wrote: + RTE_LOG(ERR, EAL, + "All memory segments exhausted by IVSHMEM. " >>> There is no evidence that it is related to IVSHMEM. >>> "

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-06-20 Thread Thomas Monjalon
2016-06-20 10:38, Sergio Gonzalez Monroy: > On 20/06/2016 10:14, Thomas Monjalon wrote: > >> + RTE_LOG(ERR, EAL, > >> + "All memory segments exhausted by IVSHMEM. " > > There is no evidence that it is related to IVSHMEM. > > "Not enough memory segments." would be more appr

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-06-20 Thread Thomas Monjalon
2016-06-16 16:52, Slawomir Mrozowicz: > Overrunning array mcfg->memseg of 256 44-byte elements > at element index 257 using index j. > Fixed by add condition with message information. > > Fixes: af75078fece3 ("first public release") > Coverity ID 13282 Please use this formatting: Coverity issue:

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-06-20 Thread Sergio Gonzalez Monroy
On 20/06/2016 10:14, Thomas Monjalon wrote: >> +RTE_LOG(ERR, EAL, >> +"All memory segments exhausted by IVSHMEM. " > There is no evidence that it is related to IVSHMEM. > "Not enough memory segments." would be more appropriate. Actually we would hit this issue when

[dpdk-dev] [PATCH v5] eal: out-of-bounds write

2016-06-16 Thread Slawomir Mrozowicz
Overrunning array mcfg->memseg of 256 44-byte elements at element index 257 using index j. Fixed by add condition with message information. Fixes: af75078fece3 ("first public release") Coverity ID 13282 Signed-off-by: Slawomir Mrozowicz --- v5: - update message v4: - remove check condition from