From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: X86 ML <x86@kernel.org>, Borislav Petkov <bpetkov@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 0/5] Minor selftests improvements
Date: Tue, 7 Nov 2017 11:13:22 +0100 [thread overview]
Message-ID: <20171107101322.jkywyydiummjlvsk@gmail.com> (raw)
In-Reply-To: <cover.1509794321.git.luto@kernel.org>
* Andy Lutomirski <luto@kernel.org> wrote:
> This improves and robustifies the ldt_gdt test and fixes compiler warnings
> in the protection_keys test.
>
> Andy Lutomirski (5):
> selftests/x86/protection_keys: Fix syscall NR redefinition warnings
> selftests/x86/ldt_gdt: Robustify against set_thread_area() and LAR
> oddities
> selftests/x86/ldt_gdt: Add infrastructure to test set_thread_area()
> selftests/x86/ldt_gdt: Run most existing LDT test cases against the
> GDT as well
> selftests/x86/ldt_get: Add a few additional tests for limits
>
> tools/testing/selftests/x86/ldt_gdt.c | 88 +++++++++++++++++++++------
> tools/testing/selftests/x86/protection_keys.c | 24 ++++++--
> 2 files changed, 88 insertions(+), 24 deletions(-)
I'm still getting this build failure when typing 'make' in tools/testing/selftests/x86:
gcc -m32 -o /home/mingo/tip/tools/testing/selftests/x86/protection_keys_32 -O2 -g -std=gnu99 -pthread -Wall -no-pie protection_keys.c -lrt -ldl -lm
In file included from /usr/include/signal.h:57:0,
from protection_keys.c:33:
protection_keys.c: In function ‘signal_handler’:
protection_keys.c:253:6: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘.’ token
u64 si_pkey;
^
protection_keys.c:253:6: error: expected expression before ‘.’ token
...
Makefile:47: recipe for target '/home/mingo/tip/tools/testing/selftests/x86/protection_keys_32' failed
Plus I'm also getting these warnings even with all your fixes applied:
gcc -m32 -o /home/mingo/tip/tools/testing/selftests/x86/mpx-mini-test_32 -O2 -g -std=gnu99 -pthread -Wall -no-pie mpx-mini-test.c -lrt -ldl -lm
mpx-mini-test.c: In function ‘insn_test_failed’:
mpx-mini-test.c:1406:3: warning: array subscript is above array bounds [-Warray-bounds]
printf("bte[1]: %lx\n", bte->contents[1]);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mpx-mini-test.c:1407:3: warning: array subscript is above array bounds [-Warray-bounds]
printf("bte[2]: %lx\n", bte->contents[2]);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mpx-mini-test.c:1408:3: warning: array subscript is above array bounds [-Warray-bounds]
printf("bte[3]: %lx\n", bte->contents[3]);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks,
Ingo
prev parent reply other threads:[~2017-11-07 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 11:19 [PATCH 0/5] Minor selftests improvements Andy Lutomirski
2017-11-04 11:19 ` [PATCH 1/5] selftests/x86/protection_keys: Fix syscall NR redefinition warnings Andy Lutomirski
2017-11-07 10:16 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2017-11-04 11:19 ` [PATCH 2/5] selftests/x86/ldt_gdt: Robustify against set_thread_area() and LAR oddities Andy Lutomirski
2017-11-07 10:17 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2017-11-04 11:19 ` [PATCH 3/5] selftests/x86/ldt_gdt: Add infrastructure to test set_thread_area() Andy Lutomirski
2017-11-07 10:17 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2017-11-04 11:19 ` [PATCH 4/5] selftests/x86/ldt_gdt: Run most existing LDT test cases against the GDT as well Andy Lutomirski
2017-11-07 10:17 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2017-11-04 11:19 ` [PATCH 5/5] selftests/x86/ldt_get: Add a few additional tests for limits Andy Lutomirski
2017-11-07 10:18 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2017-11-07 10:13 ` Ingo Molnar [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=20171107101322.jkywyydiummjlvsk@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=bpetkov@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).