From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH] x86/PoD: fix (un)locking after 24772:28edc2b31a9b Date: Mon, 13 Aug 2012 13:42:07 +0100 Message-ID: <5028F61F.6080403@eu.citrix.com> References: <50290B0C0200007800094750@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50290B0C0200007800094750@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 (Xen.org)" , Andres Lagar-Cavilla , xen-devel List-Id: xen-devel@lists.xenproject.org On 13/08/12 13:11, Jan Beulich wrote: > That c/s introduced a double unlock on the out-of-memory error path of > p2m_pod_demand_populate(). > > Signed-off-by: Jan Beulich Good catch. Acked-by: George Dunlap > > --- a/xen/arch/x86/mm/p2m-pod.c > +++ b/xen/arch/x86/mm/p2m-pod.c > @@ -1075,6 +1075,7 @@ out_of_memory: > printk("%s: Out of populate-on-demand memory! tot_pages %" PRIu32 " pod_entries %" PRIi32 "\n", > __func__, d->tot_pages, p2m->pod.entry_count); > domain_crash(d); > + return -1; > out_fail: > pod_unlock(p2m); > return -1; > > >