From: Wang Nan <wangnan0@huawei.com>
To: <masami.hiramatsu.pt@hitachi.com>, <tixy@linaro.org>
Cc: <linux@arm.linux.org.uk>, <will.deacon@arm.com>,
<dave.long@linaro.org>, <taras.kondratiuk@linaro.org>,
<ben.dooks@codethink.co.uk>, <cl@linux.com>, <rabin@rab.in>,
<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <lizefan@huawei.com>
Subject: [PATCH 0/4] ARM: kprobes: introduces instruction checker.
Date: Sat, 25 Oct 2014 14:42:49 +0800 [thread overview]
Message-ID: <1414219373-20070-1-git-send-email-wangnan0@huawei.com> (raw)
This patch series is part of the version 7 of patch 'ARM: kprobes:
enable OPTPROBES for ARM 32.'. Its main goal is introducing checker
mechanism to give a chance to detail check each probed instructions.
Based on Masami Hiramatsu's suggestion, I make it a dedicated series.
Previous discussions can be found in following threads:
https://lkml.org/lkml/2014/10/22/254
https://lkml.org/lkml/2014/8/27/255
https://lkml.org/lkml/2014/8/12/12
https://lkml.org/lkml/2014/8/8/992
https://lkml.org/lkml/2014/8/8/5
https://lkml.org/lkml/2014/8/5/63
Different from v6, this version redesign checker to make it use seprate
tables other than K/Uprobe action tables, because checkers are not
K/Uprobt specific.
Patch 4/4 in this series also fix a minor bug in kprobe: original ARM
kprobe allows probing on instructions like 'str r0, [sp, r1]', which is
unsafe because we are unable to determine the stack space required to be
protected. However, this bug exists since 2007, and gcc for ARM
actually doesn't generate code like it.
Wang Nan (4):
ARM: kprobes: seprates load and store actions
ARM: kprobes: introduces checker
ARM: kprobes: collects stack consumption for store instructions
ARM: kprobes: disallow probing stack consuming instructions
arch/arm/include/asm/probes.h | 1 +
arch/arm/kernel/kprobes-arm.c | 6 +-
arch/arm/kernel/kprobes-test-arm.c | 17 ++--
arch/arm/kernel/kprobes-test-thumb.c | 13 +++
arch/arm/kernel/kprobes-thumb.c | 18 ++--
arch/arm/kernel/kprobes.c | 23 ++++-
arch/arm/kernel/kprobes.h | 3 +-
arch/arm/kernel/probes-arm.c | 41 +++++++--
arch/arm/kernel/probes-arm.h | 10 ++-
arch/arm/kernel/probes-thumb.c | 168 ++++++++++++++++++++++++++++++-----
arch/arm/kernel/probes-thumb.h | 26 ++++--
arch/arm/kernel/probes.c | 115 +++++++++++++++++++++++-
arch/arm/kernel/probes.h | 24 ++++-
arch/arm/kernel/uprobes-arm.c | 6 +-
arch/arm/kernel/uprobes.c | 2 +-
15 files changed, 412 insertions(+), 61 deletions(-)
--
1.8.4
next reply other threads:[~2014-10-25 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 6:42 Wang Nan [this message]
2014-10-25 6:42 ` [PATCH 1/4] ARM: kprobes: seprates load and store actions Wang Nan
2014-10-25 6:42 ` [PATCH 2/4] ARM: kprobes: introduces checker Wang Nan
2014-10-25 6:42 ` [PATCH 3/4] ARM: kprobes: collects stack consumption for store instructions Wang Nan
2014-10-28 16:46 ` Jon Medhurst (Tixy)
2014-10-25 6:42 ` [PATCH 4/4] ARM: kprobes: disallow probing stack consuming instructions Wang Nan
2014-10-28 12:00 ` Jon Medhurst (Tixy)
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=1414219373-20070-1-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=ben.dooks@codethink.co.uk \
--cc=cl@linux.com \
--cc=dave.long@linaro.org \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=rabin@rab.in \
--cc=taras.kondratiuk@linaro.org \
--cc=tixy@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
all inboxes | Powered by JetHome®