From: Masami Hiramatsu <mhiramat@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: mhiramat@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Dan Rue <dan.rue@linaro.org>, Matt Hart <matthew.hart@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Daniel Diaz <daniel.diaz@linaro.org>
Subject: [PATCH 0/3] arm64: kprobes: Fix some bugs in arm64 kprobes
Date: Thu, 18 Jul 2019 14:43:26 +0900 [thread overview]
Message-ID: <156342860634.8565.14804606041960884732.stgit@devnote2> (raw)
Hi,
Here are the patches which fixes kprobe bugs on arm64.
Naresh reported that recently ftracetest crashes kernel, and I found
there are 3 different bugs around the crash.
- Kprobes on arm64 doesn't recover pstate.D mask even if probed
context masks pstate.D. This causes a real kernel crash if a
kprobe is nested.
- Some symbols which are called from blacklisted function, are not
blacklisted.
- Debug exception handlers on arm64 is using rcu_read_lock(). This
doesn't crashes kernel, but kicks suspicious RCU usage warning if
we put kprobes on the function which is called in idle context.
This series includes fixes for above bugs.
Thank you,
---
Masami Hiramatsu (3):
arm64: kprobes: Recover pstate.D in single-step exception handler
arm64: unwind: Prohibit probing on return_address()
arm64: debug: Remove rcu_read_lock from debug exception
arch/arm64/kernel/debug-monitors.c | 14 ++++++++------
arch/arm64/kernel/probes/kprobes.c | 9 ++++++---
arch/arm64/kernel/return_address.c | 4 +++-
arch/arm64/kernel/stacktrace.c | 3 +++
4 files changed, 20 insertions(+), 10 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2019-07-18 5:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 5:43 Masami Hiramatsu [this message]
2019-07-18 5:43 ` [PATCH 1/3] arm64: kprobes: Recover pstate.D in single-step exception handler Masami Hiramatsu
2019-07-19 10:07 ` James Morse
2019-07-20 6:22 ` Masami Hiramatsu
2019-07-18 5:43 ` [PATCH 2/3] arm64: unwind: Prohibit probing on return_address() Masami Hiramatsu
2019-07-18 5:43 ` [PATCH 3/3] arm64: debug: Remove rcu_read_lock from debug exception Masami Hiramatsu
2019-07-18 6:22 ` Paul E. McKenney
2019-07-18 9:20 ` Mark Rutland
2019-07-18 14:31 ` Masami Hiramatsu
2019-07-19 8:42 ` James Morse
2019-07-20 7:32 ` Masami Hiramatsu
2019-07-21 1:50 ` Masami Hiramatsu
2019-07-19 9:59 ` Mark Rutland
2019-07-20 7:54 ` Masami Hiramatsu
2019-07-24 10:45 ` 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=156342860634.8565.14804606041960884732.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dan.rue@linaro.org \
--cc=daniel.diaz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=will.deacon@arm.com \
/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).