From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Rybchenko Subject: Re: [PATCH] malloc: don't skip pad on free Date: Thu, 19 Jul 2018 19:37:59 +0300 Message-ID: References: <038143a314345e9c5bf76b1287497a5c4c9f63ed.1531992860.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , To: Anatoly Burakov , Return-path: In-Reply-To: <038143a314345e9c5bf76b1287497a5c4c9f63ed.1531992860.git.anatoly.burakov@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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