From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] mempool: don't leak ring on failure Date: Tue, 24 Jun 2014 10:40:57 -0700 Message-ID: <20140624104057.1fa81fd6@nehalam.linuxnetplumber.net> References: <20140624084948.6d4ab3cd@nehalam.linuxnetplumber.net> <2601191342CEEE43887BDE71AB977258213340B1@IRSMSX105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Ananyev, Konstantin" Return-path: In-Reply-To: <2601191342CEEE43887BDE71AB977258213340B1-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Tue, 24 Jun 2014 16:16:02 +0000 "Ananyev, Konstantin" 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.