From: patchwork-bot+linux-riscv@kernel.org
To: Fabian Vogt <fvogt@suse.de>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
guoren@kernel.org, marvin.friedrich@suse.com, alex@ghiti.fr,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, bjorn@kernel.org
Subject: Re: [PATCH] riscv: kprobes: Fix probe address validation
Date: Fri, 10 Oct 2025 02:27:19 +0000 [thread overview]
Message-ID: <176006323925.354358.7825559946978649755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6191817.lOV4Wx5bFT@fvogt-thinkpad>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Wed, 10 Sep 2025 17:25:13 +0200 you wrote:
> When adding a kprobe such as "p:probe/tcp_sendmsg _text+15392192",
> arch_check_kprobe would start iterating all instructions starting from
> _text until the probed address. Not only is this very inefficient, but
> literal values in there (e.g. left by function patching) are
> misinterpreted in a way that causes a desync.
>
> Fix this by doing it like x86: start the iteration at the closest
> preceding symbol instead of the given starting point.
>
> [...]
Here is the summary with links:
- riscv: kprobes: Fix probe address validation
https://git.kernel.org/riscv/c/9e68bd803fac
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-10 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 15:25 [PATCH] riscv: kprobes: Fix probe address validation Fabian Vogt
2025-09-16 9:25 ` Guo Ren
2025-10-10 2:27 ` patchwork-bot+linux-riscv [this message]
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=176006323925.354358.7825559946978649755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=fvogt@suse.de \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marvin.friedrich@suse.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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