From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] kprobes updates for v5.8
Date: Mon, 1 Jun 2020 15:08:06 +0200 [thread overview]
Message-ID: <20200601130806.GA746506@gmail.com> (raw)
Linus,
Please pull the latest core/kprobes git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-kprobes-2020-06-01
# HEAD: 66e9b0717102507e64f638790eaece88765cc9e5 kprobes: Prevent probes in .noinstr.text section
Various kprobes updates, mostly centered around cleaning up the no-instrumentation
logic, instead of the current per debug facility blacklist, use the more generic
.noinstr.text approach, combined with a 'noinstr' marker for functions.
Also add instrumentation_begin()/end() to better manage the exact place in entry
code where instrumentation may be used.
Also add a kprobes blacklist for modules.
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
------------------>
Masami Hiramatsu (4):
kprobes: Lock kprobe_mutex while showing kprobe_blacklist
kprobes: Support __kprobes blacklist in modules
kprobes: Support NOKPROBE_SYMBOL() in modules
samples/kprobes: Add __kprobes and NOKPROBE_SYMBOL() for handlers.
Thomas Gleixner (2):
vmlinux.lds.h: Create section for protection against instrumentation
kprobes: Prevent probes in .noinstr.text section
arch/powerpc/kernel/vmlinux.lds.S | 1 +
include/asm-generic/sections.h | 3 ++
include/asm-generic/vmlinux.lds.h | 10 +++++
include/linux/compiler.h | 53 +++++++++++++++++++++++
include/linux/compiler_types.h | 4 ++
include/linux/module.h | 8 ++++
kernel/kprobes.c | 85 ++++++++++++++++++++++++++++++++++++-
kernel/module.c | 10 +++++
samples/kprobes/kprobe_example.c | 6 ++-
samples/kprobes/kretprobe_example.c | 2 +
scripts/mod/modpost.c | 2 +-
11 files changed, 180 insertions(+), 4 deletions(-)
next reply other threads:[~2020-06-01 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 13:08 Ingo Molnar [this message]
2020-06-01 19:56 ` [GIT PULL] kprobes updates for v5.8 Linus Torvalds
2020-06-04 7:19 ` [PATCH] compiler.h: Move instrumentation_begin()/end() into new <linux/instrumentation.h> header Ingo Molnar
2020-06-04 8:19 ` Ingo Molnar
2020-06-04 9:38 ` Peter Zijlstra
2020-06-05 14:35 ` Ingo Molnar
2020-07-24 12:02 ` [tip: core/headers] compiler.h: Move instrumentation_begin()/end() to " tip-bot2 for Ingo Molnar
2020-06-01 21:55 ` [GIT PULL] kprobes updates for v5.8 pr-tracker-bot
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=20200601130806.GA746506@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.