From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Li zeming <zeming@nfschina.com>,
Masami Hiramatsu (Google) <mhiramat@kernel.org>,
Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>,
Ze Gao <zegao2021@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Fixes for 6.5-rc1
Date: Tue, 11 Jul 2023 23:47:28 +0900 [thread overview]
Message-ID: <20230711234728.e9f386a44657240b7e1cda49@kernel.org> (raw)
Hi Linus,
Probes fixes and clean ups for v6.5-rc1:
- Fix fprobe's rethook release timing issue(1). Release rethook after
ftrace_ops is unregistered so that the rethook is not accessed after
free.
- Fix fprobe's rethook access timing issue(2). Stop rethook before
ftrace_ops is unregistered so that the rethook is NOT keep using
after exiting the unregister_fprobe().
- Fix eprobe cleanup logic. If it attaches to multiple events and failes
to enable one of them, rollback all enabled events correctly.
- Fix fprobe to unlock ftrace recursion lock correctly when it missed
by another running kprobe.
- Cleanup kprobe to remove unnecessary NULL.
- Cleanup kprobe to remove unnecessary 0 initializations.
Please pull the latest probes-fixes-v6.5-rc1 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.5-rc1
Tag SHA1: 18caf0b93d8c36dbef8de1332b50ea3a6defd19f
Head SHA1: 195b9cb5b288fec1c871ef89f78cc9a7461aad3a
Jiri Olsa (1):
fprobe: Release rethook after the ftrace_ops is unregistered
Li zeming (2):
kprobes: Remove unnecessary ‘NULL’ values from correct_ret_addr
kernel: kprobes: Remove unnecessary ‘0’ values
Masami Hiramatsu (Google) (1):
fprobe: Ensure running fprobe_exit_handler() finished before calling rethook_free()
Tzvetomir Stoyanov (VMware) (1):
kernel/trace: Fix cleanup logic of enable_trace_eprobe
Ze Gao (1):
fprobe: add unlock to match a succeeded ftrace_test_recursion_trylock
----
include/linux/rethook.h | 1 +
kernel/kprobes.c | 8 ++++----
kernel/trace/fprobe.c | 15 +++++++--------
kernel/trace/rethook.c | 13 +++++++++++++
kernel/trace/trace_eprobe.c | 18 ++++++++++++++++--
5 files changed, 41 insertions(+), 14 deletions(-)
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2023-07-11 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 14:47 Masami Hiramatsu [this message]
2023-07-12 23:28 ` 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=20230711234728.e9f386a44657240b7e1cda49@kernel.org \
--to=mhiramat@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tz.stoyanov@gmail.com \
--cc=zegao2021@gmail.com \
--cc=zeming@nfschina.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®