linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wangnan0@huawei.com (Wang Nan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] ARM: kprobes: introduces instruction checker.
Date: Sat, 22 Nov 2014 16:40:09 +0800	[thread overview]
Message-ID: <1416645613-38904-1-git-send-email-wangnan0@huawei.com> (raw)

This the 4th version of instruction checker patch. Version 10 of ARM
OPTPROBE patch series can be rebase to this series cleanly.

Previous discussion can be found from:

https://lkml.org/lkml/2014/11/21/55
https://lkml.org/lkml/2014/11/18/26
https://lkml.org/lkml/2014/10/25/48
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

Thanks to Tixy, he found some bugs in my previous checker decoding
table and fixed it. He also provided some more test cases about
probing stack consuming instructions. See patch 4/4.

Jon Medhurst (1):
  ARM: kprobes: Add test cases for stack consuming instructions

Wang Nan (3):
  ARM: kprobes: introduces checker
  ARM: kprobes: collects stack consumption for store instructions
  ARM: kprobes: disallow probing stack consuming instructions

 arch/arm/include/asm/kprobes.h           |   1 -
 arch/arm/include/asm/probes.h            |  13 ++++
 arch/arm/kernel/Makefile                 |   6 +-
 arch/arm/kernel/entry-armv.S             |   3 +-
 arch/arm/kernel/kprobes-arm.c            |   3 +
 arch/arm/kernel/kprobes-test-arm.c       |  29 ++++++--
 arch/arm/kernel/kprobes-test-thumb.c     |  12 ++++
 arch/arm/kernel/kprobes-thumb.c          |   4 ++
 arch/arm/kernel/kprobes.c                |  15 ++++-
 arch/arm/kernel/kprobes.h                |   7 +-
 arch/arm/kernel/probes-arm.c             |   5 +-
 arch/arm/kernel/probes-arm.h             |   3 +-
 arch/arm/kernel/probes-checkers-arm.c    |  99 ++++++++++++++++++++++++++++
 arch/arm/kernel/probes-checkers-common.c | 101 ++++++++++++++++++++++++++++
 arch/arm/kernel/probes-checkers-thumb.c  | 110 +++++++++++++++++++++++++++++++
 arch/arm/kernel/probes-checkers.h        |  54 +++++++++++++++
 arch/arm/kernel/probes-thumb.c           |  10 +--
 arch/arm/kernel/probes-thumb.h           |   6 +-
 arch/arm/kernel/probes.c                 |  70 ++++++++++++++++++--
 arch/arm/kernel/probes.h                 |  11 +++-
 arch/arm/kernel/uprobes.c                |   2 +-
 21 files changed, 533 insertions(+), 31 deletions(-)
 create mode 100644 arch/arm/kernel/probes-checkers-arm.c
 create mode 100644 arch/arm/kernel/probes-checkers-common.c
 create mode 100644 arch/arm/kernel/probes-checkers-thumb.c
 create mode 100644 arch/arm/kernel/probes-checkers.h

-- 
1.8.4

             reply	other threads:[~2014-11-22  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22  8:40 Wang Nan [this message]
2014-11-22  8:40 ` [PATCH v4 1/4] ARM: kprobes: introduces checker Wang Nan
2014-11-22  8:40 ` [PATCH v4 2/4] ARM: kprobes: collects stack consumption for store instructions Wang Nan
2014-11-27 10:08   ` Masami Hiramatsu
2014-11-22  8:40 ` [PATCH v4 3/4] ARM: kprobes: disallow probing stack consuming instructions Wang Nan
2014-11-22  8:40 ` [PATCH v4 4/4] ARM: kprobes: Add test cases for " Wang Nan

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=1416645613-38904-1-git-send-email-wangnan0@huawei.com \
    --to=wangnan0@huawei.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).