From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com
 [209.85.220.50]) by dpdk.org (Postfix) with ESMTP id 7A4B4B0AE
 for <dev@dpdk.org>; Tue, 24 Jun 2014 19:40:42 +0200 (CEST)
Received: by mail-pa0-f50.google.com with SMTP id bj1so543201pad.9
 for <dev@dpdk.org>; Tue, 24 Jun 2014 10:41:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=bCjXBo2RPP/y90ue1OunIEa1qG+YmhImtGw0aT9ryfE=;
 b=VXtiy42K6yot3ZM5wdOxFAKqYFBbB5/dEff4XjlwWyI02USMyvIxgplZ0PMjnszW++
 SfvplfWnIKvq+9/S3GP+ycpGV/m8N3mlVLY/gRkOk/Mys8T+ZivykTerG2VeLTBbuor1
 dd4OsDVzSWb+8Gcy25l4e9s6bgj9+vU8vYKr5QclOFZsLqMfGTEO+DdeCcR6JNh1skYa
 n3jW6Z0rReVAhFc0z+ktIvKmuZw2462tX8csZAmLtNXkqmvOTzcPjlu+hwKVPVHWwlP5
 U7p2Qb8OUAFgF7gGg4pHuTvx2ZNr9SKIcEKTXZZBWPibo7a0TA60JQhD1Z1DgC4IVUzY
 //Aw==
X-Gm-Message-State: ALoCoQmnAYSSBPMA4Evc3OuThnDFNhVYKAt3Qkln6TXmiKiD+Xvu0XijsyVzed1lZzTOQaadS6Rk
X-Received: by 10.68.186.130 with SMTP id fk2mr3764188pbc.60.1403631660200;
 Tue, 24 Jun 2014 10:41:00 -0700 (PDT)
Received: from nehalam.linuxnetplumber.net
 (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51])
 by mx.google.com with ESMTPSA id nh8sm1384524pbc.25.2014.06.24.10.40.59
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Tue, 24 Jun 2014 10:40:59 -0700 (PDT)
Date: Tue, 24 Jun 2014 10:40:57 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Message-ID: <20140624104057.1fa81fd6@nehalam.linuxnetplumber.net>
In-Reply-To: <2601191342CEEE43887BDE71AB977258213340B1@IRSMSX105.ger.corp.intel.com>
References: <20140624084948.6d4ab3cd@nehalam.linuxnetplumber.net>
 <2601191342CEEE43887BDE71AB977258213340B1@IRSMSX105.ger.corp.intel.com>
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mempool: don't leak ring on failure
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 17:40:42 -0000

On Tue, 24 Jun 2014 16:16:02 +0000
"Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:

> But now, memzone created for the actual mempool could get leaked instead?

Since memzone's can't be destroyed, then only solution would be if
checked if memzone with same name already exists.