Re: [dpdk-dev] [PATCH v2] Correctly handle malloc_elem resize with padding

2017-06-08 Thread Lavigne, Jamie
Hi Sergio, > Hi Jamie, > > On 31/05/2017 01:16, Jamie Lavigne wrote: > > Currently when a malloc_elem is split after resizing, any padding > > present in the elem is ignored. This causes the resized elem to be too > > small when padding is present, and user data can overwrite the beginning

Re: [dpdk-dev] [PATCH v2] Correctly handle malloc_elem resize with padding

2017-06-06 Thread Sergio Gonzalez Monroy
Hi Jamie, On 31/05/2017 01:16, Jamie Lavigne wrote: Currently when a malloc_elem is split after resizing, any padding present in the elem is ignored. This causes the resized elem to be too small when padding is present, and user data can overwrite the beginning of the following malloc_elem. So

[dpdk-dev] [PATCH v2] Correctly handle malloc_elem resize with padding

2017-05-30 Thread Jamie Lavigne
Currently when a malloc_elem is split after resizing, any padding present in the elem is ignored. This causes the resized elem to be too small when padding is present, and user data can overwrite the beginning of the following malloc_elem. Solve this by including the size of the padding when comp