From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: oleg@redhat.com, mhiramat@kernel.org, peterz@infradead.org,
andrii@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
x86@kernel.org, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, haoluo@google.com, rostedt@goodmis.org,
mingo@kernel.org
Subject: Re: [PATCHv4 bpf-next 0/6] uprobe,bpf: Allow to change app registers from uprobe registers
Date: Wed, 24 Sep 2025 09:50:14 +0000 [thread overview]
Message-ID: <175870741477.2114834.11872828252359824573.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916215301.664963-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 16 Sep 2025 23:52:55 +0200 you wrote:
> hi,
> we recently had several requests for tetragon to be able to change
> user application function return value or divert its execution through
> instruction pointer change.
>
> This patchset adds support for uprobe program to change app's registers
> including instruction pointer.
>
> [...]
Here is the summary with links:
- [PATCHv4,bpf-next,1/6] bpf: Allow uprobe program to change context registers
https://git.kernel.org/bpf/bpf-next/c/7384893d970e
- [PATCHv4,bpf-next,2/6] uprobe: Do not emulate/sstep original instruction when ip is changed
https://git.kernel.org/bpf/bpf-next/c/4363264111e1
- [PATCHv4,bpf-next,3/6] selftests/bpf: Add uprobe context registers changes test
https://git.kernel.org/bpf/bpf-next/c/7f8a05c5d388
- [PATCHv4,bpf-next,4/6] selftests/bpf: Add uprobe context ip register change test
https://git.kernel.org/bpf/bpf-next/c/6a4ea0d1cb44
- [PATCHv4,bpf-next,5/6] selftests/bpf: Add kprobe write ctx attach test
https://git.kernel.org/bpf/bpf-next/c/1b881ee294b2
- [PATCHv4,bpf-next,6/6] selftests/bpf: Add kprobe multi write ctx attach test
https://git.kernel.org/bpf/bpf-next/c/3d237467a444
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-09-24 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 21:52 [PATCHv4 bpf-next 0/6] uprobe,bpf: Allow to change app registers from uprobe registers Jiri Olsa
2025-09-16 21:52 ` [PATCHv4 bpf-next 1/6] bpf: Allow uprobe program to change context registers Jiri Olsa
2025-09-16 21:52 ` [PATCHv4 bpf-next 2/6] uprobe: Do not emulate/sstep original instruction when ip is changed Jiri Olsa
2025-09-16 22:28 ` Andrii Nakryiko
2025-09-22 20:47 ` Andrii Nakryiko
2025-09-24 8:49 ` Peter Zijlstra
2025-09-24 9:47 ` Alexei Starovoitov
2025-09-24 10:23 ` Jiri Olsa
2025-09-16 21:52 ` [PATCHv4 bpf-next 3/6] selftests/bpf: Add uprobe context registers changes test Jiri Olsa
2025-09-16 21:52 ` [PATCHv4 bpf-next 4/6] selftests/bpf: Add uprobe context ip register change test Jiri Olsa
2025-09-16 21:53 ` [PATCHv4 bpf-next 5/6] selftests/bpf: Add kprobe write ctx attach test Jiri Olsa
2025-09-16 21:53 ` [PATCHv4 bpf-next 6/6] selftests/bpf: Add kprobe multi " Jiri Olsa
2025-09-24 9:50 ` patchwork-bot+netdevbpf [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=175870741477.2114834.11872828252359824573.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=x86@kernel.org \
--cc=yhs@fb.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