From: Markus Boehme <markubo@amazon.com>
To: stable@vger.kernel.org
Cc: Markus Boehme <markubo@amazon.com>
Subject: [PATCH 5.15 0/2] tracing/kprobes: Fix symbol counting logic by looking at modules as well
Date: Thu, 11 Jan 2024 22:43:52 +0100 [thread overview]
Message-ID: <20240111214354.369299-1-markubo@amazon.com> (raw)
This backports the fix to the kprobe_events interface allowing to create
kprobes on symbols defined in loadable modules again. The backport is
simpler than ones for later kernels, since the backport of the commit
introducing the bug already brought along much of the code needed to fix
it.
Andrii Nakryiko (1):
tracing/kprobes: Fix symbol counting logic by looking at modules as
well
Jiri Olsa (1):
kallsyms: Make module_kallsyms_on_each_symbol generally available
include/linux/module.h | 9 +++++++++
kernel/module.c | 2 --
kernel/trace/trace_kprobe.c | 2 ++
3 files changed, 11 insertions(+), 2 deletions(-)
--
2.40.1
next reply other threads:[~2024-01-11 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 21:43 Markus Boehme [this message]
2024-01-11 21:43 ` [PATCH 5.15 1/2] kallsyms: Make module_kallsyms_on_each_symbol generally available Markus Boehme
2024-01-11 21:43 ` [PATCH 5.15 2/2] tracing/kprobes: Fix symbol counting logic by looking at modules as well Markus Boehme
2024-01-13 9:32 ` [PATCH 5.15 0/2] " Greg KH
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=20240111214354.369299-1-markubo@amazon.com \
--to=markubo@amazon.com \
--cc=stable@vger.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