From: Francis Laniel <flaniel@linux.microsoft.com>
To: stable@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Francis Laniel <flaniel@linux.microsoft.com>
Subject: [PATCH 5.15.y 0/1] Return EADDRNOTAVAIL when func matches several symbols
Date: Mon, 23 Oct 2023 15:22:16 +0300 [thread overview]
Message-ID: <20231023122217.302483-1-flaniel@linux.microsoft.com> (raw)
In-Reply-To: <2023102127-unbeaten-sandlot-da45@gregkh>
Hi!
Applying the upstream patch leaded to compilation error regarding
kallsyms_on_each_match_symbol().
So, I adapted the patch to use kallsyms_on_each_symbol() instead:
root@vm-amd64:~# uname -a
Linux vm-amd64 5.15.136+ #126 SMP Mon Oct 23 15:18:02 EEST 2023 x86_64 GNU/Linux
root@vm-amd64:~# echo 'p:probe/name_show name_show' > /sys/kernel/tracing/kprobe_events
bash: echo: write error: Cannot assign requested address
As I modified the patch, I would like to get some reviews before it lands in
stable.
Francis Laniel (1):
tracing/kprobes: Return EADDRNOTAVAIL when func matches several
symbols
kernel/trace/trace_kprobe.c | 74 +++++++++++++++++++++++++++++++++++++
kernel/trace/trace_probe.h | 1 +
2 files changed, 75 insertions(+)
Best regards and thank you in advance.
--
2.34.1
next prev parent reply other threads:[~2023-10-23 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 20:03 FAILED: patch "[PATCH] tracing/kprobes: Return EADDRNOTAVAIL when func matches" failed to apply to 5.15-stable tree gregkh
2023-10-23 12:22 ` Francis Laniel [this message]
2023-10-23 12:22 ` [PATCH 5.15.y 1/1] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Francis Laniel
2023-11-27 17:32 ` [PATCH 5.15.y] " Francis Laniel
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=20231023122217.302483-1-flaniel@linux.microsoft.com \
--to=flaniel@linux.microsoft.com \
--cc=mhiramat@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.