qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [PULL v2][ALSO STABLE] balloon: multiple fixes and cleanups


From: Amit Shah
Subject: [Qemu-devel] [PULL v2][ALSO STABLE] balloon: multiple fixes and cleanups
Date: Thu, 28 Jul 2011 15:19:46 +0530
User-agent: Mutt/1.5.21 (2010-09-15)

Hello,

This new pull request carries the first 7 patches from the earlier
pull request that cleaned up balloon code and fixed a use-after-free
segfault on issuing 'balloon 0'.

This series adds 5 more patches that fix:
 - a memleak on unplug, 
 - migration after unplug,
 - negative balloon values by rejecting them

It also rejects creating multiple balloon devices.

Please pull.

Makes sense to pull these in for stable as well.

The following changes since commit c886edfb851c0c590d4e77f058f2ec8ed95ad1b5:

  Let users select their pythons (2011-07-25 16:50:12 +0000)

are available in the git repository at:
  git://git.kernel.org/pub/scm/virt/qemu/amit/misc.git for-anthony

Amit Shah (12):
      balloon: Make functions, local vars static
      balloon: Add braces around if statements
      balloon: Simplify code flow
      virtio-balloon: Separate status handling into separate function
      balloon: Separate out stat and balloon handling
      balloon: Fix header comment; add Copyright
      virtio-balloon: Fix header comment; add Copyright
      balloon: Don't allow multiple balloon handler registrations
      virtio-balloon: Check if balloon registration failed
      balloon: Reject negative balloon values
      virtio-balloon: Add exit handler, fix memleaks
      virtio-balloon: Unregister savevm section on device unplug

 balloon.c           |   61 ++++++++++++++++++++++++++---------------
 balloon.h           |   12 +++-----
 hw/virtio-balloon.c |   76 ++++++++++++++++++++++++++++++++++-----------------
 hw/virtio-pci.c     |   14 +++++++++-
 hw/virtio.h         |    1 +
 5 files changed, 109 insertions(+), 55 deletions(-)


                Amit



reply via email to

[Prev in Thread] Current Thread [Next in Thread]