From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Jan Beulich <JBeulich@suse.com>,
mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@alien8.de>, Stas Sergeev <stsp@list.ru>
Subject: Re: [PATCH] x86: add UMIP support
Date: Thu, 17 Nov 2016 15:27:43 -0800 [thread overview]
Message-ID: <1479425263.2692.11.camel@ranerica-desktop> (raw)
In-Reply-To: <20161117065213.GA10358@gmail.com>
Hi Jan,
On Thu, 2016-11-17 at 07:52 +0100, Ingo Molnar wrote:
> * Jan Beulich <JBeulich@suse.com> wrote:
>
> > This is a small aid to security, hiding in particular the kernel address
> > information otherwise available through SGDT/SIDT.
> >
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
> > ---
> > Main question here is whether to limit this to 64-bit (or at least
> > !CONFIG_VM86) for the time being, or to disable it while running VM86
> > mode code: Such code isn't unlikely to use SMSW (and one of SGDT/SIDT)
> > to figure out whether it's running on an i286 or i386, as the EFLAGS
> > based method recommended by Intel's SDM can't be relied upon there.
For vm86, the consensus now is to emulate these instructions by trapping
the GP fault that UMIP causes with these instructions and give the user
space fake pointers to SGDT/SIDT. In this way we hide these tables and
the vm86 application does not see the fault.
I am finishing v2 of my patches and I will send them shortly.
Thanks and BR,
Ricardo
> > ---
> > Documentation/kernel-parameters.txt | 4 ++++
> > arch/x86/include/asm/cpufeatures.h | 1 +
> > arch/x86/include/uapi/asm/processor-flags.h | 2 ++
> > arch/x86/kernel/cpu/common.c | 16 +++++++++++++++-
> > 4 files changed, 22 insertions(+), 1 deletion(-)
>
> Note that similar patches have been submitted a week ago:
>
> https://lkml.org/lkml/2016/11/8/68
>
> Thanks,
>
> Ingo
prev parent reply other threads:[~2016-11-17 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 15:44 [PATCH] x86: add UMIP support Jan Beulich
2016-11-17 6:52 ` Ingo Molnar
2016-11-17 23:27 ` Ricardo Neri [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=1479425263.2692.11.camel@ranerica-desktop \
--to=ricardo.neri-calderon@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=stsp@list.ru \
--cc=tglx@linutronix.de \
/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