From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Andrii Nakryiko" <andrii@kernel.org>,
"Carlos López" <clopez@suse.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Fixes for v6.10-rc1
Date: Tue, 28 May 2024 08:10:44 +0900 [thread overview]
Message-ID: <20240528081044.aa2ad32fbec8e15e2144d5f4@kernel.org> (raw)
Hi Linus,
Probes fixes for v6.10-rc1:
- uprobes: prevent mutex_lock() under rcu_read_lock(). Recent changes moves
uprobe_cpu_buffer preparation which involves mutex_lock(), under
__uprobe_trace_func() which is called inside rcu_read_lock(). Fix it
by moving uprobe_cpu_buffer preparation outside of __uprobe_trace_func().
- kprobe-events: Fix to handle the error case of btf_find_struct_member().
Please pull the latest probes-fixes-v6.10-rc1 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.10-rc1
Tag SHA1: bb80683f3a93708ce63bae89b6c712a1a8ff1c43
Head SHA1: e569eb34970281438e2b48a3ef11c87459fcfbcb
Andrii Nakryiko (1):
uprobes: prevent mutex_lock() under rcu_read_lock()
Carlos López (1):
tracing/probes: fix error check in parse_btf_field()
----
kernel/trace/trace_probe.c | 4 ++++
kernel/trace/trace_uprobe.c | 14 +++++++++-----
2 files changed, 13 insertions(+), 5 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2024-05-27 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 23:10 Masami Hiramatsu [this message]
2024-05-28 18:08 ` [GIT PULL] probes: Fixes for v6.10-rc1 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=20240528081044.aa2ad32fbec8e15e2144d5f4@kernel.org \
--to=mhiramat@kernel.org \
--cc=andrii@kernel.org \
--cc=clopez@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox