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.4.y 0/1] Return EADDRNOTAVAIL when func matches several symbols during kprobe creation
Date: Mon, 23 Oct 2023 14:36:22 +0300 [thread overview]
Message-ID: <20231023113623.36423-1-flaniel@linux.microsoft.com> (raw)
In-Reply-To: <2023102137-mobster-sheath-bfb3@gregkh>
Hi.
There was problem to apply upstream patch on kernel 5.4.
I adapted the patch and came up with the attached one, it was tested and
validated:
root@vm-amd64:~# uname -a
Linux vm-amd64 5.4.258+ #121 SMP Mon Oct 23 14:22:43 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 had to modify the patch, I would like to get reviews before getting it
merged 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 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 19:30 FAILED: patch "[PATCH] tracing/kprobes: Return EADDRNOTAVAIL when func matches" failed to apply to 5.4-stable tree gregkh
2023-10-23 11:36 ` Francis Laniel [this message]
2023-10-23 11:36 ` [PATCH 5.4.y 1/1] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Francis Laniel
2023-10-31 14:16 ` [PATCH 5.4.y 0/1] Return EADDRNOTAVAIL when func matches several symbols during kprobe creation Greg KH
2023-10-31 20:59 ` Francis Laniel
2023-11-27 17:09 ` [PATCH 5.4.y] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols 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=20231023113623.36423-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.