From: "Jan Beulich" <JBeulich@novell.com>
To: rshriram@cs.ubc.ca
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate)
Date: Tue, 10 May 2011 16:02:29 +0100 [thread overview]
Message-ID: <4DC96FA50200007800040C69@vpn.id2.novell.com> (raw)
In-Reply-To: <BANLkTinURoEKajLD54zQQVNf1=7uKaXb3A@mail.gmail.com>
>>> On 10.05.11 at 16:52, Shriram Rajagopalan <rshriram@cs.ubc.ca> wrote:
> On Tue, May 10, 2011 at 3:41 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
>> The most plausible looking EOPNOTSUPP from that code is in
>> xen/arch/x86/domain.c:arch_set_info_guest() but that is on a PV only
>> path.
>>
>> And that rings with the pv guests I am using. It makes perfect sense,
> looking
> at that function and especially at the code that returns EOPNOTSUPP (the
> only
> place in the entire file).
> else
> {
> bool_t fail = v->arch.pv_vcpu.ctrlreg[3] != c(ctrlreg[3]);
>
> #ifdef CONFIG_X86_64
> fail |= v->arch.pv_vcpu.ctrlreg[1] != c(ctrlreg[1]);
> #endif
>
> for ( i = 0; i < ARRAY_SIZE(v->arch.pv_vcpu.gdt_frames); ++i )
> fail |= v->arch.pv_vcpu.gdt_frames[i] != c(gdt_frames[i]);
> fail |= v->arch.pv_vcpu.gdt_ents != c(gdt_ents);
>
> fail |= v->arch.pv_vcpu.ldt_base != c(ldt_base);
> fail |= v->arch.pv_vcpu.ldt_ents != c(ldt_ents);
>
> if ( fail )
> return -EOPNOTSUPP;
> }
>
> This change was introduced by c/s
> changeset: 23142:f5e8d152a565
> user: Jan Beulich <jbeulich@novell.com>
> date: Tue Apr 05 13:01:25 2011 +0100
> x86: split struct vcpu
>
> I think I am missing something really obvious in this piece of code. The
> xc_domain_resume code tries to modify the return value of shutdown hypercall
> (i.e eax register is set to 1) and this code doesnt seem to check those
> registers.
Correct - the code here checks only for values where the logic
needed to support changing the on an already initialized vCPU isn't
implemented. Previously, actual vCPU state and what was tracked
in struct vcpu could get out of sync in this case, potentially
confusing things further down (including possible security issues).
You'll want to figure out which part(s) actually differ, and why.
Only then we'll be able to tell whether mentioned c/s introduced
false positives.
Jan
next prev parent reply other threads:[~2011-05-10 15:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 23:06 xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate) Shriram Rajagopalan
2011-05-10 8:41 ` Ian Campbell
2011-05-10 14:52 ` Shriram Rajagopalan
2011-05-10 15:02 ` Jan Beulich [this message]
2011-05-10 15:50 ` Shriram Rajagopalan
2011-05-10 15:55 ` Ian Campbell
2011-05-10 16:03 ` Jan Beulich
2011-05-11 2:30 ` Shriram Rajagopalan
2011-05-11 7:47 ` Jan Beulich
2011-05-11 18:37 ` Shriram Rajagopalan
2011-05-11 19:50 ` Shriram Rajagopalan
2011-05-13 10:00 ` Jan Beulich
2011-05-14 22:15 ` Shriram Rajagopalan
2011-05-16 12:02 ` Jan Beulich
2011-05-17 1:48 ` Shriram Rajagopalan
2011-05-24 19:24 ` AP Xen
2011-05-24 20:09 ` Keir Fraser
2011-05-25 7:15 ` Jan Beulich
2011-05-25 7:53 ` AP Xen
2011-05-12 8:10 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 6:05 Jan Beulich
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=4DC96FA50200007800040C69@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Campbell@citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xensource.com \
/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).