From: Pratyush Anand <panand@redhat.com>
To: linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-kernel@vger.kernel.org, wcohen@redhat.com,
dave.long@linaro.org, steve.capper@linaro.org,
masami.hiramatsu.pt@hitachi.com,
Pratyush Anand <panand@redhat.com>
Subject: [PATCH 0/2] arm64: some symbols blacklisted for kprobing
Date: Mon, 6 Jul 2015 10:33:20 +0530 [thread overview]
Message-ID: <cover.1436158027.git.panand@redhat.com> (raw)
Functions which are called from do_debug_execptions and all entry routines
must not allow to insert kprobe in it, otherwise we may witness a system hang.
This patch set blacklist such symbols.
Patches should be applied on top of arm64 kprobe patches [1].
[1] https://lkml.org/lkml/2015/6/15/514
Pratyush Anand (2):
arm64: Blacklist non-kprobe-able symbols
arm64: Make all entry code as non-kprobe-able
arch/arm64/kernel/debug-monitors.c | 18 ++++++++++++++++++
arch/arm64/kernel/entry.S | 3 +++
arch/arm64/kernel/hw_breakpoint.c | 8 ++++++++
arch/arm64/kernel/kgdb.c | 4 ++++
arch/arm64/kernel/kprobes.c | 9 +++++++++
arch/arm64/kernel/vmlinux.lds.S | 1 +
arch/arm64/mm/fault.c | 1 +
7 files changed, 44 insertions(+)
--
2.4.3
next reply other threads:[~2015-07-06 5:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 5:03 Pratyush Anand [this message]
2015-07-06 5:03 ` [PATCH 1/2] arm64: Blacklist non-kprobe-able symbols Pratyush Anand
2015-07-06 9:03 ` Will Deacon
2015-07-06 10:48 ` Pratyush Anand
2015-07-06 11:56 ` Masami Hiramatsu
2015-07-06 11:37 ` Masami Hiramatsu
2015-07-06 14:42 ` William Cohen
2015-07-06 11:11 ` Masami Hiramatsu
2015-07-06 11:49 ` Pratyush Anand
2015-07-09 13:53 ` Pratyush Anand
2015-07-06 5:03 ` [PATCH 2/2] arm64: Make all entry code as non-kprobe-able Pratyush Anand
2015-07-06 11:03 ` Masami Hiramatsu
2015-07-06 11:54 ` Pratyush Anand
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.1436158027.git.panand@redhat.com \
--to=panand@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=steve.capper@linaro.org \
--cc=wcohen@redhat.com \
--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).