From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Li Hua <hucool.lihua@huawei.com>,
Li Huafei <lihuafei1@huawei.com>,
wuqiang <wuqiang.matt@bytedance.com>
Subject: Re: [GIT PULL] tracing probes: Updates for 6.2
Date: Tue, 20 Dec 2022 11:51:17 -0500 [thread overview]
Message-ID: <20221220115117.2052d9a0@gandalf.local.home> (raw)
In-Reply-To: <20221216094254.7876461d@gandalf.local.home>
On Fri, 16 Dec 2022 09:42:54 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Linus,
>
> As Masami is still working on getting his gpg key working with signed tags
> and such, he asked me to send his pull request on his behalf until he gets
> that straighten out.
>
> Trace probes updates for 6.2:
Hi Linus,
Just wanted to make sure that this didn't get missed.
Thanks,
-- Steve
>
> - New "symstr" type for dynamic events that writes the name of the
> function+offset into the ring buffer and not just the address
>
> - Prevent kernel symbol processing on addresses in user space probes
> (uprobes).
>
> - And minor fixes and clean ups
>
>
> Please pull the latest trace-probes-v6.2 tree, which can be found at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
> trace-probes-v6.2
>
> Tag SHA1: ce1e1e9588758069e9b19ce97941133aa826699c
> Head SHA1: d4505aa6afae17a20c2f3ccfbfb7a07881b7ae02
>
>
> Li Hua (1):
> test_kprobes: Fix implicit declaration error of test_kprobes
>
> Li Huafei (1):
> kprobes: Fix check for probe enabled in kill_kprobe()
>
> Masami Hiramatsu (Google) (2):
> tracing/probes: Add symstr type for dynamic events
> tracing/probes: Reject symbol/symstr type for uprobe
>
> Steven Rostedt (Google) (1):
> tracing: Fix race where eprobes can be called before the event
>
> wuqiang (1):
> kprobes: kretprobe events missing on 2-core KVM guest
>
> ----
> Documentation/trace/kprobes.rst | 3 +-
> Documentation/trace/kprobetrace.rst | 8 ++-
> kernel/kprobes.c | 24 ++++----
> kernel/trace/trace.c | 2 +-
> kernel/trace/trace_eprobe.c | 3 +
> kernel/trace/trace_probe.c | 65 ++++++++++++++--------
> kernel/trace/trace_probe.h | 19 +++++--
> kernel/trace/trace_probe_tmpl.h | 47 +++++++++++++++-
> kernel/trace/trace_uprobe.c | 3 +-
> lib/Kconfig.debug | 1 +
> .../ftrace/test.d/kprobe/uprobe_syntax_errors.tc | 5 ++
> 11 files changed, 128 insertions(+), 52 deletions(-)
> ---------------------------
next prev parent reply other threads:[~2022-12-20 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 14:42 Steven Rostedt
2022-12-20 16:51 ` Steven Rostedt [this message]
2022-12-22 3:07 ` 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=20221220115117.2052d9a0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hucool.lihua@huawei.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wuqiang.matt@bytedance.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®