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

Re: [Xen-devel] [PATCH 0 of 12] backport critical fixes from qemu upstream

  • To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  • From: Mark Johnson <johnson.nh@xxxxxxxxx>
  • Date: Fri, 9 Oct 2009 08:04:32 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 09 Oct 2009 05:04:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bXt0ir7cAd8V61GyctaP+FwQ4ePVTytKahzc4mZTfdFjqeaZtLv325lWmP8pO1yyEF HFs7w4Qwhw+JoKxOQ+WhcURVwFYTAbkf5OF59d31HfzIddzn4RyhgV8VnXY2df8tC1ds 6Fu3cXSv+5aGd+XU4tfGie4HPg603O9I8Hrfw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On Mon, Oct 5, 2009 at 9:40 AM, Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> wrote:
> Hi all,
> the current qemu block layer contains few critical problems, one of them
> was fixed by "fix qemu memory leak in block interface" but unfortunately
> others remain.
> In particular every time the guest cancels a dma request qemu
> segfaults.
> In order to completely fix any remaining bug I suggest to revert the
> previous fix "fix qemu memory leak in block interface" and backport
> instead the following changesets from qemu upstream:

> The same should be done to qemu-xen-3.4-testing as well.
> Cheers,

Are you planning to push these to qemu-xen-3.4-testing  soon too?



Xen-devel mailing list



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