From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Thomas DEBESSE <thomas.debesse@diocese-frejus-toulon.com>
Cc: xen-devel@lists.xen.org
Subject: Re: DomU: kernel BUG at arch/x86/xen/enlighten.c:425
Date: Tue, 15 Sep 2015 17:35:09 +0100 [thread overview]
Message-ID: <55F848BD.90205@citrix.com> (raw)
In-Reply-To: <CAGXJp7125WKwnAORGxfV-D4c+sLsfZzs4URNKoS4Zjc7efT=CQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]
On 15/09/15 17:28, Thomas DEBESSE wrote:
> 2015-09-15 18:09 GMT+02:00 Andrew Cooper <andrew.cooper3@citrix.com
> <mailto:andrew.cooper3@citrix.com>>:
>
> The instantiation of HYPERVISOR_update_va_mapping() in
> set_aliased_prot() has always been buggy in pvops kernels.
>
> This bug should be fixed by c/s 0b0e55 "x86/xen: Probe target
> addresses in set_aliased_prot before the hypercall" which is in
> the process of being backported to #stable as a prerequisite for
> the recent LDT CVE fixes.
>
> ~Andrew
>
>
> OK thanks, I will stick with the 3.2 kernel for the moment, it seems
> to work with it.
> I don't know why, but only one vm seems to be affected (and they all
> are built the same way).
It will depend on userspace running in the VM as to whether the bug gets
tickled.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1945 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-09-15 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 16:03 DomU: kernel BUG at arch/x86/xen/enlighten.c:425 Thomas DEBESSE
2015-09-15 16:09 ` Andrew Cooper
2015-09-15 16:28 ` Thomas DEBESSE
2015-09-15 16:35 ` Andrew Cooper [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-08 2:23 James Sinclair
2013-03-08 8:38 ` Jan Beulich
[not found] ` <4A885B42-B352-4FE4-A0A7-2B10CF595E61@linode.com>
2013-03-12 7:45 ` Jan Beulich
2013-03-12 22:56 ` James Sinclair
2013-03-13 0:38 ` James Sinclair
2013-03-13 9:50 ` Ian Campbell
2013-03-18 0:27 ` James Sinclair
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=55F848BD.90205@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=thomas.debesse@diocese-frejus-toulon.com \
--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 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).