From: Andy Lutomirski <luto@kernel.org>
To: security@kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/3] Stuff for 4.2 (including a revert)
Date: Mon, 17 Aug 2015 12:22:49 -0700 [thread overview]
Message-ID: <cover.1439838962.git.luto@kernel.org> (raw)
Hi all-
Patch 1 is a revert, Cc'd to stable. I haven't tried to write a
real test for the bug, but the code definitely looks buggy. I
intent to fix it for real as part of converting more of the syscall
entry code to C, but this is a better fix for now.
Patch 2 fixes selftests fallout from the sigcontext revert.
Patch 3 is a new test that I thought I added but apparently didn't.
It's probably 4.3 material, but it's related to patch 1, so I'm
sending them together.
Andy Lutomirski (3):
Revert "sched/x86_64: Don't save flags on context switch"
selftests/x86: Disable sigreturn_64
selftests/x86: Add syscall_nt selftest
arch/x86/include/asm/switch_to.h | 12 +++----
tools/testing/selftests/x86/Makefile | 4 +--
tools/testing/selftests/x86/syscall_nt.c | 54 ++++++++++++++++++++++++++++++++
3 files changed, 60 insertions(+), 10 deletions(-)
create mode 100644 tools/testing/selftests/x86/syscall_nt.c
--
2.4.3
next reply other threads:[~2015-08-17 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 19:22 Andy Lutomirski [this message]
2015-08-17 19:22 ` [PATCH 1/3] Revert "sched/x86_64: Don't save flags on context switch" Andy Lutomirski
2015-08-19 7:09 ` [tip:x86/asm] Revert "sched/x86_64: Don' t " tip-bot for Andy Lutomirski
2015-08-17 19:22 ` [PATCH 2/3] selftests/x86: Disable sigreturn_64 Andy Lutomirski
2015-08-19 7:09 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-08-17 19:22 ` [PATCH 3/3] selftests/x86: Add syscall_nt selftest Andy Lutomirski
2015-08-19 7:10 ` [tip:x86/asm] " tip-bot for 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=cover.1439838962.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@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 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.