From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Donglin Peng <dolinux.peng@gmail.com>,
Masami Hiramatsu (Google) <mhiramat@kernel.org>,
Quanfa Fu <quanfafu@gmail.com>,
Yang Jihong <yangjihong1@huawei.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [GIT PULL] probes: Updates for 6.3
Date: Tue, 21 Feb 2023 21:14:08 +0900 [thread overview]
Message-ID: <20230221211408.6fa4bb5868cda7d506a00c61@kernel.org> (raw)
Hi Linus,
probes updates for 6.3:
- Skip negative return code check for snprintf in eprobe.
- Add recursive call test cases for kprobe unit test
- Add 'char' type to probe events to show it as the character instead of value.
- Update kselftest kprobe-event testcase to ignore '__pfx_' symbols.
- Fix kselftest to check filter on eprobe event correctly.
- Add filter on eprobe to the README file in tracefs.
- Fix optprobes to check whether there is 'under unoptimizing' optprobe when optimizing another kprobe correctly.
- Fix optprobe to check whether there is 'under unoptimizing' optprobe when fetching the original instruction correctly.
- Fix optprobe to free 'forcibly unoptimized' optprobe correctly.
Please pull the latest probes-v6.3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v6.3
Tag SHA1: 7aa067de8b9767c68e828eabb15b830175dc0325
Head SHA1: c96abaec78f34366b3ddf1c6be52ca5c1241e15b
Donglin Peng (1):
tracing/probe: add a char type to show the character value of traced arguments
Masami Hiramatsu (Google) (5):
kprobes: Fix to handle forcibly unoptimized kprobes on freeing_list
tracing/eprobe: Fix to add filter on eprobe description in README file
selftests/ftrace: Fix eprobe syntax test case to check filter support
selftests/ftrace: Fix probepoint testcase to ignore __pfx_* symbols
test_kprobes: Add recursed kprobe test case
Quanfa Fu (1):
tracing/eprobe: no need to check for negative ret value for snprintf
Yang Jihong (2):
x86/kprobes: Fix __recover_optprobed_insn check optimizing logic
x86/kprobes: Fix arch_check_optimized_kprobe check within optimized_kprobe range
----
Documentation/trace/kprobetrace.rst | 3 +-
arch/x86/kernel/kprobes/opt.c | 6 +--
include/linux/kprobes.h | 2 +
kernel/kprobes.c | 27 ++++++-------
kernel/trace/trace.c | 4 +-
kernel/trace/trace_eprobe.c | 12 ++----
kernel/trace/trace_probe.c | 2 +
kernel/trace/trace_probe.h | 1 +
lib/test_kprobes.c | 39 +++++++++++++++++-
.../test.d/dynevent/eprobes_syntax_errors.tc | 4 +-
.../ftrace/test.d/kprobe/kprobe_args_char.tc | 47 ++++++++++++++++++++++
.../selftests/ftrace/test.d/kprobe/probepoint.tc | 2 +-
12 files changed, 116 insertions(+), 33 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc
---------------------------
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2023-02-21 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:14 Masami Hiramatsu [this message]
2023-02-23 22:20 ` 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=20230221211408.6fa4bb5868cda7d506a00c61@kernel.org \
--to=mhiramat@kernel.org \
--cc=dolinux.peng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quanfafu@gmail.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=yangjihong1@huawei.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®