All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [PULL] qemu-xen stable update to 1.6.2
Date: Wed, 15 Jan 2014 14:35:05 +0000	[thread overview]
Message-ID: <20140115143504.GL1696@perard.uk.xensource.com> (raw)
In-Reply-To: <1389778510.12434.118.camel@kazak.uk.xensource.com>

On Wed, Jan 15, 2014 at 09:35:10AM +0000, Ian Campbell wrote:
> On Tue, 2014-01-14 at 18:52 +0000, Anthony PERARD wrote:
> > There is an update of QEMU 1.6, I have done a merge and put that in a tree:
> > git://xenbits.xen.org/people/aperard/qemu-dm.git  merge-1.6.2
> 
> Based on the above I have no idea whether a freeze exception should be
> granted for this, so my default answer is no. I'm not sure what else you
> could have expected.
> 
> If you think there are changes here which should be in 4.4.0 then please
> enumerate all changes included in this merge which have any relation to
> Xen and their potential impact on the release.

I have a list the change here that have a potential impact on Xen, with
the ones that I think are quite important at the beginning. Either the
commit title speak for itself or I added a small description on what is
affected.

Fix pc migration from qemu <= 1.5

- Potential compilation issue:
Adjust qapi-visit for python-2.4.3
configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0

- Memory leak:
qapi: fix memleak by adding implict struct functions in dealloc visitor
  qapi is used by qmp, so potential leaks when doing qmp call
qom: Fix memory leak in object_property_set_link()
  same for qom

qdev-monitor: Fix crash when device_add is called with abstract driver
qdev-monitor: Unref device when device_add fails
  those could be a potential issue triggered through device-add qmp
  command

qemu-char: Fix potential out of bounds access to local arrays
  for serial="vc:WxH"
  vc stand for virtual console

audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second
  looks like it improve cpu load when playing audio

scsi_target_send_command(): amend stable-1.6 port of the CVE-2013-4344 fix
  if someone use scsi disk

vmdk: Fix vmdk_parse_extents
vmdk: Fix creating big description file
  if someone use a vmdk disk image

qcow2: count_contiguous_clusters and compression
qcow2: fix possible corruption when reading multiple clusters
qcow2: Zero-initialise first cluster for new images
  several qcow2 fixes, a file disk format

virtio-net: only delete bh that existed
virtio-net: fix the memory leak in rxfilter_notify()
  few virtio fixes

rng-egd: offset the point when repeatedly read from the buffer
  looks like this can be used by virtio


I did not list the commit that does not look like a Xen guest can use.
So is this look like patches to take in our tree ? At least the first 7
would be good to take I think (migration fix, memory leaks, qdev fixes).

Regards,

-- 
Anthony PERARD

  reply	other threads:[~2014-01-15 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 18:52 [PULL] qemu-xen stable update to 1.6.2 Anthony PERARD
2014-01-15  9:35 ` Ian Campbell
2014-01-15 14:35   ` Anthony PERARD [this message]
2014-01-15 16:27     ` Ian Campbell
2014-01-16 15:42       ` Stefano Stabellini
2014-01-16 15:45         ` Stefano Stabellini
2014-01-16 15:50         ` Anthony PERARD
2014-01-16 15:51           ` Stefano Stabellini
2014-01-17 12:13             ` Anthony PERARD
2014-01-17 13:17               ` Stefano Stabellini
2014-01-17 13:43                 ` Anthony PERARD
2014-01-17 13:45                   ` Stefano Stabellini
2014-01-24 19:34                     ` Stefano Stabellini
2014-01-27 16:48                       ` George Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140115143504.GL1696@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.