All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Andy Lutomirski <luto@kernel.org>,
	x86@kernel.org, Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now
Date: Mon, 11 Jan 2016 11:59:33 +0100	[thread overview]
Message-ID: <20160111105933.GA663@gmail.com> (raw)
In-Reply-To: <568ECF61.4040007@osg.samsung.com>


* Shuah Khan <shuahkh@osg.samsung.com> wrote:

> 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.

It doesn't apply to -tip either. Andy, which tree is this against?

Thanks,

	Ingo

  reply	other threads:[~2016-01-11 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 19:51 [PATCH] selftests/x86: Disable ldt_gdt_64 for now Andy Lutomirski
2016-01-07 20:49 ` Shuah Khan
2016-01-11 10:59   ` Ingo Molnar [this message]
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=20160111105933.GA663@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=shuahkh@osg.samsung.com \
    --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 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.