[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-05-16 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Kobylinski, MichalX > Sent: Monday, May 16, 2016 1:51 PM > To: Thomas Monjalon > Cc: dev at dpdk.org; Dumitrescu, Cristian > Subject: Re: [dpdk-dev] [PATCH] cfgfile: fix integer overflo

[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-05-16 Thread Kobylinski, MichalX
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Monday, May 16, 2016 12:06 PM > To: Kobylinski, MichalX > Cc: dev at dpdk.org; Dumitrescu, Cristian > Subject: Re: [dpdk-dev] [PATCH] cfgfile: fix integer overflow > Importan

[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-05-16 Thread Thomas Monjalon
2016-04-28 11:09, Dumitrescu, Cristian: > From: Kobylinski, MichalX > > Fix issue reported by Coverity. > > > > Coverity ID 13289: Integer overflowed argument: The argument will be too > > small or even negative, likely resulting in unexpected behavior (for > > example, under-allocation in a

[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-04-28 Thread Dumitrescu, Cristian
> -Original Message- > From: Kobylinski, MichalX > Sent: Friday, April 22, 2016 11:41 AM > To: Dumitrescu, Cristian ; dev at dpdk.org > Cc: Kobylinski, MichalX > Subject: [PATCH] cfgfile: fix integer overflow > > Fix issue reported by Coverity. > > Coverity ID 13289: Integer

[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-04-22 Thread Michal Kobylinski
Fix issue reported by Coverity. Coverity ID 13289: Integer overflowed argument: The argument will be too small or even negative, likely resulting in unexpected behavior (for example, under-allocation in a memory allocation function). In rte_cfgfile_load: An integer overflow occurs, with the

[dpdk-dev] [PATCH] cfgfile: fix integer overflow

2016-04-22 Thread Stephen Hemminger
On Fri, 22 Apr 2016 12:41:01 +0200 Michal Kobylinski wrote: > Fix issue reported by Coverity. > > Coverity ID 13289: Integer overflowed argument: The argument will be too > small or even negative, likely resulting in unexpected behavior (for > example, under-allocation in a memory allocation