x86/HVM: re-order operations in hvm_ud_intercept()

Don't fetch CS explicitly, leverage the fact that hvm_emulate_prepare()
already does (and that hvm_virtual_to_linear_addr() doesn't alter it).

At once increase the length passed to hvm_virtual_to_linear_addr() by
one: There definitely needs to be at least one more opcode byte, and we
can avoid missing a wraparound case this way.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Jan Beulich committed 2016-06-17 16:50:37 +02:00
1 parent 9dec2c4740
commit d8ede4a09e
1 file changed
+14 -8
+14 -8
View File
@@ -3886,19 +3886,27 @@ void hvm_ud_intercept(struct cpu_user_regs *regs)
{
struct hvm_emulate_ctxt ctxt;
hvm_emulate_prepare(&ctxt, regs);
if ( opt_hvm_fep )
{
struct vcpu *cur = current;
struct segment_register cs;
const struct segment_register *cs = &ctxt.seg_reg[x86_seg_cs];
unsigned long addr;
char sig[5]; /* ud2; .ascii "xen" */
hvm_get_segment_register(cur, x86_seg_cs, &cs);
if ( hvm_virtual_to_linear_addr(x86_seg_cs, &cs, regs->eip,
sizeof(sig), hvm_access_insn_fetch,
/*
* Note that in the call below we pass 1 more than the signature
* size, to guard against the overall code sequence wrapping between
* "prefix" and actual instruction. There's necessarily at least one
* actual instruction byte required, so this won't cause failure on
* legitimate uses.
*/
if ( hvm_virtual_to_linear_addr(x86_seg_cs, cs, regs->eip,
sizeof(sig) + 1, hvm_access_insn_fetch,
(hvm_long_mode_enabled(cur) &&
cs.attr.fields.l) ? 64 :
cs.attr.fields.db ? 32 : 16, &addr) &&
cs->attr.fields.l) ? 64 :
cs->attr.fields.db ? 32 : 16, &addr) &&
(hvm_fetch_from_guest_virt_nofault(sig, addr, sizeof(sig),
0) == HVMCOPY_okay) &&
(memcmp(sig, "\xf\xbxen", sizeof(sig)) == 0) )
@@ -3908,8 +3916,6 @@ void hvm_ud_intercept(struct cpu_user_regs *regs)
}
}
hvm_emulate_prepare(&ctxt, regs);
switch ( hvm_emulate_one(&ctxt) )
{
case X86EMUL_UNHANDLEABLE:
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.