From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/3] probes: Updates for 6.2
Date: Sat, 10 Dec 2022 09:03:20 -0500 [thread overview]
Message-ID: <20221210140320.609495935@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes/for-next
Head SHA1: 0c76ef3f26d5ef2ac2c21b47e7620cff35809fbb
Li Hua (1):
test_kprobes: Fix implicit declaration error of test_kprobes
Li Huafei (1):
kprobes: Fix check for probe enabled in kill_kprobe()
Steven Rostedt (Google) (1):
tracing: Fix race where eprobes can be called before the event
----
kernel/kprobes.c | 16 ++++++++--------
kernel/trace/trace_eprobe.c | 3 +++
lib/Kconfig.debug | 1 +
3 files changed, 12 insertions(+), 8 deletions(-)
next reply other threads:[~2022-12-10 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 14:03 Steven Rostedt [this message]
2022-12-10 14:03 ` [for-next][PATCH 1/3] tracing: Fix race where eprobes can be called before the event Steven Rostedt
2022-12-10 14:03 ` [for-next][PATCH 3/3] kprobes: Fix check for probe enabled in kill_kprobe() Steven Rostedt
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=20221210140320.609495935@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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