From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: "Justin M. Forbes" <jforbes@redhat.com>
Subject: [Qemu-devel] [PULL v2][ALSO STABLE] balloon: multiple fixes and cleanups
Date: Thu, 28 Jul 2011 15:19:46 +0530 [thread overview]
Message-ID: <20110728094946.GF7106@amit-x200.redhat.com> (raw)
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 other threads:[~2011-07-28 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110728094946.GF7106@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=jforbes@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).