From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL] Memory core fixes
Date: Mon, 22 Oct 2012 12:11:51 +0200 [thread overview]
Message-ID: <50851BE7.8070205@redhat.com> (raw)
Please pull a few memory core fixes from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/urgent
Fixing ioeventfds on big endian systems, and potential use-after-free
(not really exploitable with the current code, but still).
----------------------------------------------------------------
Alexander Graf (1):
memory: Make eventfd adhere to device endianness
Avi Kivity (2):
i440fx: avoid destroying memory regions within a transaction
memory: abort if a memory region is destroyed during a transaction
hw/piix_pci.c | 69 +++++++++++++++++++++++++++++++++++----------------------------------
memory.c | 3 +++
2 files changed, 38 insertions(+), 34 deletions(-)
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2012-10-22 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 10:11 Avi Kivity [this message]
2012-10-23 18:08 ` [Qemu-devel] [PULL] Memory core fixes Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2012-01-08 14:01 [Qemu-devel] [PULL] memory " Avi Kivity
2012-01-09 14:51 ` Anthony Liguori
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=50851BE7.8070205@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).