From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [stable:PATCH] valid_user_regs() backport
Date: Mon, 18 Jul 2016 13:27:22 +0100 [thread overview]
Message-ID: <1468844845-6129-1-git-send-email-james.morse@arm.com> (raw)
Hi all,
These three copies of the same patch backport dbd4d7ca563f
("arm64: Rework valid_user_regs") to the stable kernels listed on kernel.org
as far back as v3.16.
This patch fixed a userspace triggerable oops when userspace tries
to switch to a mode not supported by the kernel:
[ 286.628508] Bad mode in Synchronous Abort handler detected, code 0x46000000 -- SVC (AArch32)
[ 286.639625] CPU: 3 PID: 2072 Comm: inter Not tainted 4.4.14 #4504
[ 286.648391] Hardware name: ARM Juno development board (r1) (DT)
[ ... ]
[ 286.716784] Bad mode in Synchronous Abort handler detected, code 0x86000007 -- IABT (current EL)
[ 286.725483] CPU: 3 PID: 2072 Comm: inter Not tainted 4.4.14 #4504
[ 286.731513] Hardware name: ARM Juno development board (r1) (DT)
[ ... ]
[ 286.840815] Internal error: Oops - bad mode: 0 [#1] PREEMPT SMP
[ 286.846673] Modules linked in:
[ 286.849699] CPU: 3 PID: 2072 Comm: inter Not tainted 4.4.14 #4504
[ 286.855728] Hardware name: ARM Juno development board (r1) (DT)
Thanks,
James
arch/arm64/include/asm/ptrace.h | 34 +++---------------
arch/arm64/kernel/ptrace.c | 80 +++++++++++++++++++++++++++++++++++++++--
arch/arm64/kernel/signal.c | 4 +--
arch/arm64/kernel/signal32.c | 2 +-
4 files changed, 86 insertions(+), 34 deletions(-)
--
2.8.0.rc3
next reply other threads:[~2016-07-18 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 12:27 James Morse [this message]
2016-07-18 12:27 ` [stable:PATCH] arm64: Rework valid_user_regs (v4.1+) James Morse
2016-07-18 12:27 ` [stable:PATCH] arm64: Rework valid_user_regs (v3.18) James Morse
2016-07-18 12:27 ` [stable:PATCH] arm64: Rework valid_user_regs (v3.16) James Morse
2017-10-08 21:18 ` Ben Hutchings
2016-07-18 12:59 ` [stable:PATCH] valid_user_regs() backport 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=1468844845-6129-1-git-send-email-james.morse@arm.com \
--to=james.morse@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).