From: Andrew Cooper <andrew.cooper3@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] x86/PV: properly populate descriptor tables
Date: Mon, 26 Oct 2015 14:58:43 +0000 [thread overview]
Message-ID: <562E3FA3.5030707@citrix.com> (raw)
In-Reply-To: <562E3EDF.5040502@citrix.com>
On 26/10/15 14:55, Andrew Cooper wrote:
> On 26/10/15 14:43, David Vrabel wrote:
>> On 23/09/15 16:34, Jan Beulich wrote:
>>> Us extending the GDT limit past the Xen descriptors so far meant that
>>> guests (including user mode programs) accessing any descriptor table
>>> slot above the original OS'es limit but below the first Xen descriptor
>>> caused a #PF, converted to a #GP in our #PF handler. Which is quite
>>> different from the native behavior, where some of such accesses (LAR
>>> and LSL) don't fault. Mimic that behavior by mapping a blank page into
>>> unused slots.
>>>
>>> While not strictly required, treat the LDT the same for consistency.
>> This change causes a 32-bit userspace process running in a 32-bit PV
>> guest to segfault.
>>
>> The process is a Go program and it is using the modify_ldt() system call
>> (which is successful) but loading %gs with the new descriptor causes a
>> fault. Even a minimal (empty main()) go program faults.
> D'uh - its obvious now you point it out.
>
> By filling the shadow ldt slots as present, zero entries, we break their
> demand-faulting.
>
> We can't be safe to incorrect faults from LAR/LSL, *and* perform demand
> faulting of the LDT.
Wait. Yes we can. I am talking nonsense.
Hunk 2 should be reverted, and the demand fault handler should populate
a zero entry rather than passing #GP back to the guest.
~Andrew
next prev parent reply other threads:[~2015-10-26 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 15:34 [PATCH] x86/PV: properly populate descriptor tables Jan Beulich
2015-09-23 15:47 ` Andrew Cooper
2015-09-24 16:18 ` Wei Liu
2015-10-26 14:43 ` David Vrabel
2015-10-26 14:55 ` Andrew Cooper
2015-10-26 14:58 ` Andrew Cooper [this message]
2015-10-26 15:08 ` Jan Beulich
2015-10-26 15:41 ` David Vrabel
2015-10-26 15:58 ` Jan Beulich
2015-10-26 16:02 ` David Vrabel
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=562E3FA3.5030707@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=keir@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).