Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
SUSE:SLE-12-SP2:GA
xen.5015
5888b1b3-x86-emulate-dont-assume-addr_size-32-i...
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 5888b1b3-x86-emulate-dont-assume-addr_size-32-implies-protmode.patch of Package xen.5015
# Commit 05118b1596ffe4559549edbb28bd0124a7316123 # Date 2017-01-25 15:09:55 +0100 # Author George Dunlap <george.dunlap@citrix.com> # Committer Jan Beulich <jbeulich@suse.com> x86/emulate: don't assume that addr_size == 32 implies protected mode Callers of x86_emulate() generally define addr_size based on the code segment. In vm86 mode, the code segment is set by the hardware to be 16-bits; but it is entirely possible to enable protected mode, set the CS to 32-bits, and then disable protected mode. (This is commonly called "unreal mode".) But the instruction decoder only checks for protected mode when addr_size == 16. So in unreal mode, hardware will throw a #UD for VEX prefixes, but our instruction decoder will decode them, triggering an ASSERT() further on in _get_fpu(). (With debug=n the emulator will incorrectly emulate the instruction rather than throwing a #UD, but this is only a bug, not a crash, so it's not a security issue.) Teach the instruction decoder to check that we're in protected mode, even if addr_size is 32. Signed-off-by: George Dunlap <george.dunlap@citrix.com> Split real mode and VM86 mode handling, as VM86 mode is strictly 16-bit at all times. Re-base. Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com> --- a/xen/arch/x86/x86_emulate/x86_emulate.c +++ b/xen/arch/x86/x86_emulate/x86_emulate.c @@ -1562,11 +1562,11 @@ x86_emulate( default: BUG(); case 2: - if ( in_realmode(ctxt, ops) || (_regs.eflags & EFLG_VM) ) + if ( _regs.eflags & EFLG_VM ) break; /* fall through */ case 4: - if ( modrm_mod != 3 ) + if ( modrm_mod != 3 || in_realmode(ctxt, ops) ) break; /* fall through */ case 8:
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor