[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/PoD: fix (un)locking after 24772:28edc2b31a9b


  • To: "Jan Beulich" <JBeulich@xxxxxxxx>
  • From: "Andres Lagar-Cavilla" <andres@xxxxxxxxxxxxxxxx>
  • Date: Mon, 13 Aug 2012 08:22:22 -0700
  • Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Mon, 13 Aug 2012 15:22:51 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=lagarcavilla.org; h=message-id :in-reply-to:references:date:subject:from:to:cc:reply-to :mime-version:content-type:content-transfer-encoding; q=dns; s= lagarcavilla.org; b=Ek9ueTg6ZtKLDpR/FGvE1xWP9RTy7LIg2D0gmKfNOD+r ywYkkS8+8DmYek6InCE2TtuqWhoqBofhKz7Tozsf3gBHAMgWjchXGljGsaQWXpMc GdeBBEMqn9Gsv4bW/CG46BxdNqOLJZ3NbdIhGvZXNz3Z+uins/7BxQNUN79zzxs=
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>>> On 13.08.12 at 14:11, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> That c/s introduced a double unlock on the out-of-memory error path of
>> p2m_pod_demand_populate().
>
> I also wonder how correct that changeset's elimination of the page
> alloc lock in a number of places here is - p2m_pod_set_mem_target()'s
> calculations, for example, involve d->tot_pages, which with that lock
> not held can change under its feet.

afaict, access to d->tot_pages was not protected by the page_alloc lock
even prior to 24772.

Back when, I thought those unprotected tot_pages accesses should either be
locked or atomic_read(). Slipped through the cracks.

Andres

>
> Jan
>
>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.