From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64: correctly and consistently handle Xt == XZR
Date: Thu, 9 Feb 2017 15:19:17 +0000 [thread overview]
Message-ID: <1486653561-22357-1-git-send-email-mark.rutland@arm.com> (raw)
Hi,
I spotted that we inconsistently handle the use of Xt when we trap
instructions, and in some cases we may erroneously access SP.
These patches add new helpers to handle this for us, and moves code over to
using them, fixing the erroneous SP usage in the process.
Patch 2 (correcting the trapped CTR_EL0 handling) will need backporting to
stable, and is dependent on patch 1.
Patch 3 is also a fix, but shouldn't need backporting as the patch hasn't made
it into a release yet. Patch 4 is a cleanup for consistency.
Thanks,
Mark.
Mark Rutland (4):
arm64: ptrace: add XZR-safe regs accessors
arm64: traps: correctly handle MRS/MSR with XZR
arm64: cpufeature: correctly handle MRS to XZR
arm64/kprobes: consistently handle MRS/MSR with XZR
arch/arm64/include/asm/ptrace.h | 20 ++++++++++++++++++++
arch/arm64/kernel/cpufeature.c | 2 +-
arch/arm64/kernel/probes/simulate-insn.c | 18 ++++++------------
arch/arm64/kernel/traps.c | 6 ++++--
4 files changed, 31 insertions(+), 15 deletions(-)
--
1.9.1
next reply other threads:[~2017-02-09 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 15:19 Mark Rutland [this message]
2017-02-09 15:19 ` [PATCH 1/4] arm64: ptrace: add XZR-safe regs accessors Mark Rutland
2017-02-09 15:19 ` [PATCH 2/4] arm64: traps: correctly handle MRS/MSR with XZR Mark Rutland
2017-02-09 15:19 ` [PATCH 3/4] arm64: cpufeature: correctly handle MRS to XZR Mark Rutland
2017-02-09 15:19 ` [PATCH 4/4] arm64/kprobes: consistently handle MRS/MSR with XZR Mark Rutland
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=1486653561-22357-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).