mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Andy Lutomirski <luto@kernel.org>, x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now
Date: Thu, 7 Jan 2016 13:49:37 -0700	[thread overview]
Message-ID: <568ECF61.4040007@osg.samsung.com> (raw)
In-Reply-To: <8dd42ba6434d84eefe6d864fb453fbe34d43098c.1452109816.git.luto@kernel.org>

On 01/06/2016 12:51 PM, Andy Lutomirski wrote:
> ldt_gdt.c relies on cross-cpu invalidation of SS to do one of its
> tests.  On 32-bit builds, this works fine, but on 64-bit builds, it
> only works if the kernel has proper SS sigcontext handling for
> 64-bit user programs.
> 
> Since the SS fixes are currently reverted, restrict the test case to
> 32 bits for now.
> 
> In principle, I could change the test to use a different segment
> register, but it would be messy: CS can't point to the LDT for
> 64-bit code, and the other registers don't result in immediate
> faults because they aren't reloaded on kernel -> user transitions.
> 
> When we fix sigcontext (in 4.6?), we can revert this.
> 
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> --

Andy,

This patch didn't apply to linux-kselftest next.
It probably has to go through x86.

thanks,
-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978

  reply	other threads:[~2016-01-07 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 19:51 Andy Lutomirski
2016-01-07 20:49 ` Shuah Khan [this message]
2016-01-11 10:59   ` Ingo Molnar
2016-01-12  1:25     ` Andy Lutomirski
2016-01-12 10:45       ` Ingo Molnar

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=568ECF61.4040007@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=x86@kernel.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

Powered by JetHome