From: "Burakov, Anatoly" Subject: Re: [RFC v2] mem: poison memory when freed Date: Fri, 20 Jul 2018 14:09:10 +0100 Message-ID: References: <20180719162029.30962-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Stephen Hemminger , dev@dpdk.org Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id BB81123C for ; Fri, 20 Jul 2018 15:09:21 +0200 (CEST) In-Reply-To: <20180719162029.30962-1-stephen@networkplumber.org> 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-Jul-18 5:20 PM, Stephen Hemminger wrote: > DPDK malloc library allows broken programs to work because > the semantics of zmalloc and malloc are the same. > > This patch enables a more secure model which will catch > (and crash) programs that reuse memory already freed if > RTE_MALLOC_DEBUG is enabled. > > Signed-off-by: Stephen Hemminger > --- Making it not default behavior makes it suitable for inclusion without deprecation notices IMO. Reviewed-by: Anatoly Burakov -- Thanks, Anatoly