From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id F14F11DB9;
 Sun, 18 Nov 2018 14:15:14 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 81F0421CF3;
 Sun, 18 Nov 2018 08:15:14 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
 by compute1.internal (MEProxy); Sun, 18 Nov 2018 08:15:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding:content-type; s=mesmtp;
 bh=Zr2Orlflmorohk1ednBcxRwLWlxF5LlIY4YxnqJJK+U=; b=mntEcXiIreRA
 tkIbAVn31ypFHffwUi9yxauXX3yxKOb8baaj/Mp1kT4TsGbxOwNRExPHiU9UHkt/
 4/Sm3Ne5AOkNYWIBMUqsTB1taiEzhmki5voI+lzk6Z+16Wy5QT+/1W5SuyKO+bqe
 QagYsJz8IDXxntYMFXnSZp0dG2TRjQw=
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-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm1; bh=Zr2Orlflmorohk1ednBcxRwLWlxF5LlIY4YxnqJJK
 +U=; b=kcoGdqcxZd2EmsNEHXxSlidl3vRqLc3BIbegV4nHCE/G5nzirVbTewe0/
 9E2eVJP4usM5Q9+EFYJLFE6MhLn3m/Pd1/2GBIDCnaXFQoj1LWGbeExqB6VxYFS4
 tQhMhfkiGn5wF+jBas5LtSkBbGy8k1Ylhp6ogQ9Q8deJnhzwfvq0zA/3Id8KzQUA
 bNwcgJlHgKwM68dOsMwSM1G0DvFSPP2Tueag3dvM1SMznkgf0kn905xiNqsVGAd4
 YvU0umFFQ1W7+Va7i+bgs2G5XMbljpKGsaZ+Cx4DmgvlbpulkjjGYZQclunMYj79
 64K2HLc4u4YepbGi0TFwxkYhR5QPA==
X-ME-Sender: <xms:4WXxW2UDcsQlNvsm_NukQxwZPzsgLioHJ7ZAe7P5pg06YDUYGCaarg>
X-ME-Proxy: <xmx:4WXxW88f9sapiKBPnFdChosXSP2GHKmb5tcPCnG0agKpzP_QneCXDg>
 <xmx:4WXxWzOvyDmRt1fPj7b24qBzcaA0YQVUJ0lImIW73I0kpWvFJyOeeQ>
 <xmx:4WXxW82RTqg6lGKvDbKpRnw2spxGWctOi3JzHSis7emPVVplcAwTuQ>
 <xmx:4WXxWyrO5FTTv6GSFyZ3J8IlichMwaYNu9jKkFdmdu0Ojov_YP9OFw>
 <xmx:4WXxW8uMolz5yV2qynwAuMH6ttX_q9fFEEy90A8EUcZMCKiVutEfcg>
 <xmx:4mXxW95nJvtMoqD5RC8TppBNRLfaWe8meHfJwJoVZEvi8ZNNm6lhDA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id ED439102F2;
 Sun, 18 Nov 2018 08:15:12 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, yuwei1.zhang@intel.com, stable@dpdk.org
Date: Sun, 18 Nov 2018 14:15:12 +0100
Message-ID: <2233776.yr2cuDNz4j@xps>
In-Reply-To: <6a0a1a54d58a7c72380860c1da9e36d512c0ccd2.1542207435.git.anatoly.burakov@intel.com>
References: <8533ab3a49f63e9700764ead8b9147a098911b41.1542204687.git.anatoly.burakov@intel.com>
 <6a0a1a54d58a7c72380860c1da9e36d512c0ccd2.1542207435.git.anatoly.burakov@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v2] malloc: fix adjacency check to also
	include segment list
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Nov 2018 13:15:15 -0000

14/11/2018 16:00, Anatoly Burakov:
> It may so happen that two memory locations may be adjacent in
> virtual memory, but belong to different segment lists. With
> current code, such segments will be concatenated. Fix the
> adjacency checking code to also check if the adjacent malloc
> elements belong to the same memseg list.
> 
> Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks