From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] malloc: don't skip pad on free Date: Fri, 20 Jul 2018 11:27:43 +0200 Message-ID: <2958510.WtYFjzW1qE@xps> References: <038143a314345e9c5bf76b1287497a5c4c9f63ed.1531992860.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Andrew Rybchenko , stephen@networkplumber.org, stable@dpdk.org To: Anatoly Burakov Return-path: In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 19/07/2018 18:37, Andrew Rybchenko: > On 19.07.2018 12:42, Anatoly Burakov wrote: > > Previously, we were skipping erasing pad because we were > > expecting it to be freed when we were merging adjacent > > segments. However, if there were no adjacent segments to > > merge, we would've skipped erasing the pad, leaving non-zero > > memory in our free space. > > > > Fix this by including pad in the erasing unconditionally. > > > > Fixes: e43a9f52b7ff ("malloc: fix pad erasing") > > Cc: stable@dpdk.org > > > > Reported-by: Andrew Rybchenko > > > > Signed-off-by: Anatoly Burakov > > Many thanks, the patch fixes the problem I've observed. > > Tested-by: Andrew Rybchenko Applied, thanks