Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1303032 > unrolled thread

[PATCH] selftests/x86: Disable ldt_gdt_64 for now

Back to article view | Back to linux.kernel

Contents

  [PATCH] selftests/x86: Disable ldt_gdt_64 for now Andy Lutomirski <luto@kernel.org> - 2016-01-06 21:00 +0100
    Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now Shuah Khan <shuahkh@osg.samsung.com> - 2016-01-07 21:50 +0100
      Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now Ingo Molnar <mingo@kernel.org> - 2016-01-11 12:00 +0100
        Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now Andy Lutomirski <luto@amacapital.net> - 2016-01-12 02:30 +0100
          Re: [PATCH] selftests/x86: Disable ldt_gdt_64 for now Ingo Molnar <mingo@kernel.org> - 2016-01-12 11:50 +0100

#1303032 — [PATCH] selftests/x86: Disable ldt_gdt_64 for now

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>
---
 tools/testing/selftests/x86/Makefile | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/x86/Makefile b/tools/testing/selftests/x86/Makefile
index 3d1a8ef500a0..c0c15ff179b7 100644
--- a/tools/testing/selftests/x86/Makefile
+++ b/tools/testing/selftests/x86/Makefile
@@ -4,10 +4,11 @@ include ../lib.mk
 
 .PHONY: all all_32 all_64 warn_32bit_failure clean
 
-TARGETS_C_BOTHBITS := single_step_syscall sysret_ss_attrs ldt_gdt syscall_nt ptrace_syscall
+TARGETS_C_BOTHBITS := single_step_syscall sysret_ss_attrs syscall_nt ptrace_syscall
 TARGETS_C_32BIT_ONLY := entry_from_vm86 syscall_arg_fault sigreturn test_syscall_vdso unwind_vdso \
 			test_FCMOV test_FCOMI test_FISTTP \
-			vdso_restorer
+			vdso_restorer \
+			ldt_gdt
 
 TARGETS_C_32BIT_ALL := $(TARGETS_C_BOTHBITS) $(TARGETS_C_32BIT_ONLY)
 BINARIES_32 := $(TARGETS_C_32BIT_ALL:%=%_32)
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1303888

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

[toc] | [prev] | [next] | [standalone]

#1306069

* 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

[toc] | [prev] | [next] | [standalone]

#1306890

On Mon, Jan 11, 2016 at 2:59 AM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * 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?

Oops, it applies on top of a new self-test that I forgot to send.  I
send a v2 that should be better.  I'll send the new selftest out as
well once -tip catches up with all the vdso patches.

--Andy

[toc] | [prev] | [next] | [standalone]

#1307251

* Andy Lutomirski <luto@amacapital.net> wrote:

> On Mon, Jan 11, 2016 at 2:59 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * 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?
> 
> Oops, it applies on top of a new self-test that I forgot to send.  I
> send a v2 that should be better.  I'll send the new selftest out as
> well once -tip catches up with all the vdso patches.

Ok, sounds great!

Thanks,

	Ingo

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web