From: "Salva Peiró" <speirofr@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] memory: Add function pointers checks to memory_region_read/write()
Date: Tue, 28 Jul 2015 09:13:19 +0200 [thread overview]
Message-ID: <1438067600-8468-1-git-send-email-speirofr@gmail.com> (raw)
The situation where QEMU crashes while attempting to call to a NULL
function pointer from a non-initialised field in the MemoryRegionOps
struct happens for the majority of emulated devices:
One approach for solving this is to correct it for each device.
The other approach is to correct the memory_region_read/write caller
functions at memory.c to ensure that only initialised function pointers
are being called. This approach has the benefit of solving this kind of
error for all emulated devices.
The following patch adds function pointers checks to memory_region_read/write()
next reply other threads:[~2015-07-28 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 7:13 Salva Peiró [this message]
2015-07-28 7:13 ` [Qemu-devel] [PATCH] memory: Add function pointers checks to memory_region_read/write() Salva Peiró
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=1438067600-8468-1-git-send-email-speirofr@gmail.com \
--to=speirofr@gmail.com \
--cc=pbonzini@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).