From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 9C8042BE1 for ; Wed, 28 Jun 2017 23:12:43 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EF6202057E; Wed, 28 Jun 2017 17:12:42 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 28 Jun 2017 17:12:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=6IDDBIgiLc56KHa i9G3HSr1A0KYWF/F6u5nRjpmEfw4=; b=GDoujUND3Ai+neGGMzhseqZlxBEbQ39 cP7vHDQbOt/yQxnAXFQQOqi4/3WCPr8a2RQwq65QMAM56pl67RwHpiq9fXVFvBEM ff1xoBTAvtOSoFYSlqXE97CXNDr5xqXTOnIzAk9KAYZxlYE/dVD9kAEnDQYTi7Nk bojvWtSOB/Uc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=6IDDBIgiLc56KHai9G3HSr1A0KYWF/F6u5nRjpmEfw4=; b=EiZkXqaz q97/aaKeKI8q6uf2139e2VhDSR7J8ZIQL7D07c5OPgzboC6dWRWuPRPgXwOArPJu eGEIGV/Xwy/hl6TA5wolFq91yKLYrs7PCtxVQfxBijVszlMIZkprTVX8AH97eIR4 jUX0HSEqAg9Nx3y7G/yzc7ikBkEUBdcQfqZHhGJF2ItqSSOfp5uJMNqdG7jX2nYv U0AXK8Qt3EftN/oot0npIbF+XctQCvj4dxDT1uIKZHsM9pnE26muNqqEQLAUhcv2 GgU/ba+Pq6k853dPZ8eVzMbAg/8dPqCZ6pvAxo252aSyyR2RYR8WCvCH/EnggzTO GQ+sAs7mkbD3aA== X-ME-Sender: X-Sasl-enc: JhXLGvA40p+kMDmW1IYJJgtxqVQQrXUCBIpusSAPNqGc 1498684362 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A000B2436B; Wed, 28 Jun 2017 17:12:42 -0400 (EDT) From: Thomas Monjalon To: Jamie Lavigne Cc: dev@dpdk.org, Sergio Gonzalez Monroy Date: Wed, 28 Jun 2017 23:12:41 +0200 Message-ID: <1743355.dtpiII7vli@xps> In-Reply-To: <2e4d0d34-626c-0ac2-6c46-c2b1086c3397@intel.com> References: <1496189818-2307-1-git-send-email-lavignen@amazon.com> <1496949137-8106-1-git-send-email-lavignen@amazon.com> <2e4d0d34-626c-0ac2-6c46-c2b1086c3397@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] mem: fix malloc_elem resize with padding X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jun 2017 21:12:43 -0000 20/06/2017 12:18, Sergio Gonzalez Monroy: > On 08/06/2017 20:12, 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. > > > > Solve this by including the size of the padding when computing where to > > split the malloc_elem. > > > > Fixes: af75078fece3 ("first public release") > > > > Signed-off-by: Jamie Lavigne > > Acked-by: Sergio Gonzalez Monroy Applied, thanks