From: Thomas Gleixner <tglx@linutronix.de>
To: Jan Beulich <jbeulich@suse.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: x86: insn-eval.c's use of native_store_gdt()
Date: Fri, 04 Feb 2022 15:08:30 +0100 [thread overview]
Message-ID: <87fsoyd8rl.ffs@tglx> (raw)
In-Reply-To: <68c4f398-0494-e272-47e0-6803b6865f15@suse.com>
On Fri, Feb 04 2022 at 10:23, Jan Beulich wrote:
> On 30.11.2021 12:09, Jan Beulich wrote:
>> I think it is b968e84b509d ("x86/iopl: Fake iopl(3) CLI/STI usage")
>> which uncovered an issue with get_desc() trying to access the GDT, as
>> introduced by 670f928ba09b ("x86/insn-eval: Add utility function to
>> get segment descriptor"). When running in a PV domain under Xen, the
>> (hypervisor's) GDT isn't accessible; with UMIP enabled by Xen even
>> SGDT wouldn't work, as the kernel runs in ring 3.
>>
>> There's currently no hypercall to retrieve a descriptor from the GDT.
>> It is instead assumed that kernels know where their present GDT
>> lives. Can the native_store_gdt() be replaced there, please?
>>
>> For context (I don't think it should matter much here) I'm observing
>> this with the kernel put underneath a rather old distro, where
>> hwclock triggers this path.
>
> I'd like to note that the issue still exists in 5.16.
I'd like to note, that I've seen no patches to that effect.
Thanks,
tglx
next prev parent reply other threads:[~2022-02-04 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 11:09 x86: insn-eval.c's use of native_store_gdt() Jan Beulich
2022-02-04 9:23 ` Jan Beulich
2022-02-04 14:08 ` Thomas Gleixner [this message]
2022-02-04 14:13 ` Jan Beulich
2022-02-05 3:09 ` Ricardo Neri
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=87fsoyd8rl.ffs@tglx \
--to=tglx@linutronix.de \
--cc=jbeulich@suse.com \
--cc=peterz@infradead.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=x86@kernel.org \
--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 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.