From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/2] x86/64: espfix64 cleanups and testing
Date: Mon, 12 Sep 2016 15:05:49 -0700 [thread overview]
Message-ID: <cover.1473717910.git.luto@kernel.org> (raw)
This tidies up ESPFIX a bit and improves the test case slightly.
Andy Lutomirski (2):
selftests/x86/sigreturn: Use CX, not AX, as the scratch register
x86/entry/64: Clean up and document espfix64 stack setup
arch/x86/entry/entry_64.S | 64 +++++++++++++++++++++++++++------
tools/testing/selftests/x86/sigreturn.c | 16 ++++-----
2 files changed, 61 insertions(+), 19 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-12 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:05 Andy Lutomirski [this message]
2016-09-12 22:05 ` [PATCH 1/2] selftests/x86/sigreturn: Use CX, not AX, as the scratch register Andy Lutomirski
2016-09-13 22:08 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2016-09-12 22:05 ` [PATCH 2/2] x86/entry/64: Clean up and document espfix64 stack setup Andy Lutomirski
2016-09-13 22:08 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2016-09-13 9:04 ` [PATCH 0/2] x86/64: espfix64 cleanups and testing Borislav Petkov
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.1473717910.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox