From: Ian Campbell <ian.campbell@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@suse.com>,
"security@xen.org" <security@xen.org>
Subject: Re: [PATCH] x86/vmx: Fix injection of #DB traps following XSA-156
Date: Tue, 5 Jan 2016 14:52:05 +0000 [thread overview]
Message-ID: <1452005525.13361.297.camel@citrix.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F764444@SHSMSX101.ccr.corp.intel.com>
On Tue, 2016-01-05 at 06:53 +0000, Tian, Kevin wrote:
> > From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
> > Sent: Monday, January 04, 2016 6:00 PM
> >
> > Most #DB exceptions are traps rather than faults, meaning that the
> > instruction
> > pointer in the exception frame points after the instruction rather than
> > at it.
> >
> > However, VMX intercepts all have fault semantics, even when
> > intercepting a
> > trap. Re-injecting an intercepted trap as a fault causes an infinite
> > loop in
> > the guest, by re-executing the same trapping instruction
> > repeatedly. This
> > breaks debugging inside the guest.
> >
> > Introduce a helper which copies VM_EXIT_INTR_INTO to
> > VM_ENTRY_INTR_INFO, and
> > use it to mirror the intercepted interrupt back to the guest.
> >
> > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Acked-by: Kevin Tian <kevin.tian@intel.com>
Thanks. Andy tells me this issue is causing quite some havoc in the field
and we aren't sure when Jan is back from vacation so I have stepped outside
the usual scope of things I commit and applied this one. I hope that's OK
with everyone.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-01-05 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 9:59 [PATCH] x86/vmx: Fix injection of #DB traps following XSA-156 Andrew Cooper
2016-01-05 6:53 ` Tian, Kevin
2016-01-05 14:52 ` Ian Campbell [this message]
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=1452005525.13361.297.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=security@xen.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.