From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org
Subject: [Qemu-devel] [PATCH 0/2] target/i386: trap on instructions longer than >15 bytes
Date: Thu, 12 Oct 2017 16:35:46 +0200 [thread overview]
Message-ID: <20171012143548.18581-1-pbonzini@redhat.com> (raw)
This is an improved (and more invasive) fix for the bug fixed in
commit 30663fd ("tcg/i386: Check the size of instruction being
translated", 2017-03-24).
Paolo Bonzini (2):
target/i386: introduce x86_ld*_code
target/i386: trap on instructions longer than >15 bytes
target/i386/translate.c | 257 +++++++++++++++++++++++++++---------------------
1 file changed, 147 insertions(+), 110 deletions(-)
--
2.14.2
next reply other threads:[~2017-10-12 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 14:35 Paolo Bonzini [this message]
2017-10-12 14:35 ` [Qemu-devel] [PATCH 1/2] target/i386: introduce x86_ld*_code Paolo Bonzini
2017-10-12 16:30 ` Richard Henderson
2017-10-12 14:35 ` [Qemu-devel] [PATCH 2/2] target/i386: trap on instructions longer than >15 bytes Paolo Bonzini
2017-10-12 19:30 ` Richard Henderson
2017-10-12 21:43 ` Paolo Bonzini
2017-10-13 18:12 ` Richard Henderson
2017-10-12 16:55 ` [Qemu-devel] [PATCH 0/2] " no-reply
2017-10-12 19:07 ` no-reply
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=20171012143548.18581-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).