From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH v3] x86/nhvm: properly clean up after failure to set up all vCPU-s Date: Thu, 21 Feb 2013 15:42:47 +0100 Message-ID: <20130221144247.GA23819@aepfle.de> References: <51262DB302000078000BFF3D@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <51262DB302000078000BFF3D@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tim Deegan , Eddie Dong , Jun Nakajima , xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Feb 21, Jan Beulich wrote: > Otherwise we may leak memory when setting up nHVM fails half way. > > This implies that the individual destroy functions will have to remain > capable (in the VMX case they first need to be made so, following > 26486:7648ef657fe7 and 26489:83a3fa9c8434) of being called for a vCPU > that the corresponding init function was never run on. > > Once at it, also remove a redundant check from the corresponding > parameter validation code. > > Signed-off-by: Jan Beulich Tested-by: Olaf Hering This one fixes the crash as well. Thanks. Olaf