From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Suleiman Souhlal <suleiman@google.com>, bpf <bpf@vger.kernel.org>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org
Subject: [PATCH 0/2] x86/kprobes: Fixes for CONFIG_RETHUNK
Date: Wed, 7 Sep 2022 09:55:11 +0900 [thread overview]
Message-ID: <166251211081.632004.1842371136165709807.stgit@devnote2> (raw)
Hi,
Here is a couple of patches to fix kprobes and optprobe to work
on the kernel with CONFIG_RETHUNK and CONFIG_SLS.
With these configs, the kernel functions may includes padding INT3 in
the function code block (body) in addition to the gaps between functions.
Since kprobes on x86 has to ensure the probe address is a function
bondary, it decodes the instructions in the function until the address.
If it finds an INT3 which is not embedded by kprobe, it stops decoding
because usually the INT3 is used for debugging as a software breakpoint
and such INT3 will replace the first byte of an original instruction.
Without recovering it, kprobes can not continue to decode it. Thus the
kprobes returns -EILSEQ as below.
# echo "p:probe/vfs_truncate_L19 vfs_truncate+98" >> kprobe_events
sh: write error: Invalid or incomplete multibyte or wide character
Actually, those INT3s are just for padding and can be ignored.
To avoid this issue, if kprobe finds an INT3, it gets the address of
next non-INT3 byte, and search a branch which jumps to the address.
If there is the branch, these INT3 will be for padding, so it can be
skipped. [1/2]
Since the optprobe has similar issue, it also skips the padding INT3
in the same way. [2/2]
With thses fixes, kprobe and optprobe can probe the kernel again with
CONFIG_RETHUNK=y.
# echo "p:probe/vfs_truncate_L19 vfs_truncate+98" >> kprobe_events
# echo 1 > events/probe/vfs_truncate_L19/enable
# cat /sys/kernel/debug/kprobes/list
ffffffff81307b52 k vfs_truncate+0x62 [OPTIMIZED]
Thank you,
---
Masami Hiramatsu (Google) (2):
x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK
x86/kprobes: Fix optprobe optimization check with CONFIG_RETHUNK
arch/x86/kernel/kprobes/common.h | 67 +++++++++++++++++++++++++++
arch/x86/kernel/kprobes/core.c | 57 +++++++++++++----------
arch/x86/kernel/kprobes/opt.c | 93 ++++++++++++++------------------------
3 files changed, 133 insertions(+), 84 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2022-09-07 0:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 0:55 Masami Hiramatsu (Google) [this message]
2022-09-07 0:55 ` [PATCH 1/2] x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK Masami Hiramatsu (Google)
2022-09-07 7:06 ` Peter Zijlstra
2022-09-07 9:01 ` [PATCH] objtool,x86: Teach decode about LOOP* instructions Peter Zijlstra
2022-09-07 9:06 ` David Laight
2022-09-07 9:40 ` Peter Zijlstra
2022-09-07 11:13 ` David Laight
2022-09-15 14:24 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2022-09-07 9:12 ` [PATCH 1/2] x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK Masami Hiramatsu
2022-09-07 9:38 ` Peter Zijlstra
2022-09-07 9:53 ` Masami Hiramatsu
2022-09-07 8:02 ` Peter Zijlstra
2022-09-07 8:11 ` Peter Zijlstra
2022-09-07 9:49 ` Masami Hiramatsu
2022-09-07 10:19 ` Peter Zijlstra
2022-09-07 11:44 ` Peter Zijlstra
2022-09-07 13:05 ` Peter Zijlstra
2022-09-07 14:14 ` Masami Hiramatsu
2022-09-07 14:27 ` Peter Zijlstra
2022-09-07 15:22 ` Masami Hiramatsu
2022-09-07 12:56 ` Peter Zijlstra
2022-09-07 13:49 ` Masami Hiramatsu
2022-09-07 14:28 ` Peter Zijlstra
2022-09-07 12:59 ` Peter Zijlstra
2022-09-07 13:53 ` Masami Hiramatsu
2022-09-07 0:55 ` [PATCH 2/2] x86/kprobes: Fix optprobe optimization " Masami Hiramatsu (Google)
2022-09-07 6:52 ` [PATCH 0/2] x86/kprobes: Fixes for CONFIG_RETHUNK Peter Zijlstra
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=166251211081.632004.1842371136165709807.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=bp@suse.de \
--cc=bpf@vger.kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=suleiman@google.com \
--cc=x86@kernel.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