From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 01/10] selftests/x86: In syscall_nt, test NT|TF as well
Date: Wed, 2 Mar 2016 13:59:52 +0100 [thread overview]
Message-ID: <20160302125952.GG16954@pd.tnic> (raw)
In-Reply-To: <98d687a7a464ba29ba493f3885f138902c6ac574.1456720860.git.luto@kernel.org>
On Sun, Feb 28, 2016 at 09:28:46PM -0800, Andy Lutomirski wrote:
> Setting TF prevents fastpath returns in most cases, which causes the
> test to fail on 32-bit kernels because 32-bit kernels do not, in
> fact, handle NT correctly on SYSENTER entries.
>
> The next patch will fix 32-bit kernels.
>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> ---
> tools/testing/selftests/x86/syscall_nt.c | 57 +++++++++++++++++++++++++++-----
> 1 file changed, 49 insertions(+), 8 deletions(-)
>
> diff --git a/tools/testing/selftests/x86/syscall_nt.c b/tools/testing/selftests/x86/syscall_nt.c
> index 60c06af4646a..a6ceff86c199 100644
> --- a/tools/testing/selftests/x86/syscall_nt.c
> +++ b/tools/testing/selftests/x86/syscall_nt.c
...
> +static void do_it(unsigned long extraflags)
> +{
> + unsigned long flags;
> +
> + set_eflags(get_eflags() | extraflags);
> syscall(SYS_getpid);
> - if (get_eflags() & X86_EFLAGS_NT) {
> - printf("[OK]\tThe syscall worked and NT is still set\n");
> - return 0;
> + flags = get_eflags();
> + if ((flags & extraflags) == extraflags) {
> + printf("[OK]\tThe syscall worked and flags are still set\n");
> } else {
> - printf("[FAIL]\tThe syscall worked but NT was cleared\n");
> - return 1;
> + printf("[FAIL]\tThe syscall worked but flags were cleared (flags = 0x%lx but expected 0x%lx set)\n",
> + flags, extraflags);
> + nerrs++;
> }
> }
> +
> +int main()
ERROR: Bad function definition - int main() should probably be int main(void)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-03-02 13:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 5:28 [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
2016-02-29 5:28 ` [PATCH 01/10] selftests/x86: In syscall_nt, test NT|TF as well Andy Lutomirski
2016-03-02 12:59 ` Borislav Petkov [this message]
2016-03-02 14:01 ` One Thousand Gnomes
2016-03-02 14:28 ` Borislav Petkov
2016-03-02 19:03 ` Andy Lutomirski
2016-03-02 19:30 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 02/10] x86/entry/compat: In SYSENTER, sink AC clearing below the existing FLAGS test Andy Lutomirski
2016-02-29 20:39 ` Borislav Petkov
2016-02-29 20:45 ` Andy Lutomirski
2016-02-29 22:09 ` Borislav Petkov
2016-02-29 22:33 ` Brian Gerst
2016-02-29 22:37 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 03/10] x86/entry/32: Filter NT and speed up AC filtering in SYSENTER Andy Lutomirski
2016-03-02 13:24 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 04/10] x86/entry/32: Restore FLAGS on SYSEXIT Andy Lutomirski
2016-02-29 5:28 ` [PATCH 05/10] x86/traps: Clear TIF_BLOCKSTEP on all debug exceptions Andy Lutomirski
2016-02-29 5:28 ` [PATCH 06/10] x86/traps: Clear DR6 early in do_debug and improve the comment Andy Lutomirski
2016-02-29 5:28 ` [PATCH 07/10] x86/entry: Vastly simplify SYSENTER TF handling Andy Lutomirski
2016-02-29 5:28 ` [PATCH 08/10] x86/entry: Only allocate space for SYSENTER_stack if needed Andy Lutomirski
2016-02-29 5:28 ` [PATCH 09/10] x86/entry/32: Simplify and fix up the SYSENTER stack #DB/NMI fixup Andy Lutomirski
2016-02-29 5:28 ` [PATCH 10/10] x86/entry/32: Add and check a stack canary for the SYSENTER stack Andy Lutomirski
2016-02-29 18:55 ` [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
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=20160302125952.GG16954@pd.tnic \
--to=bp@alien8.de \
--cc=andrew.cooper3@citrix.com \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome