Linux Trace Kernel
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	mhiramat@kernel.org, oleg@redhat.com, bpf@vger.kernel.org,
	x86@kernel.org, linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-trace-kernel@vger.kernel.org, martin.lau@linux.dev,
	eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	will@kernel.org, palmer@dabbelt.com, peterz@infradead.org,
	rtm@csail.mit.edu
Subject: Re: [PATCH bpf 0/2] bpf: Limit writable registers in uprobe context
Date: Fri, 20 Nov 2026 02:40:06 +0000	[thread overview]
Message-ID: <179514240603.3989712.15825286425363086604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118084451.12590-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 18 Nov 2026 09:44:48 +0100 you wrote:
> Hi,
> a uprobe BPF program can currently write fields in struct pt_regs that
> are loaded directly by the architecture’s return-to-user path. Some of
> these fields are restricted by ptrace, but the BPF verifier does not
> apply the same restrictions.
> 
> This series limits uprobe context writes to registers that ptrace can
> set to arbitrary values. It adds architecture-specific writable-register
> checks for arm64, riscv, and x86-64; other architectures default to
> allowing no writes. Reads are unchanged.
> 
> [...]

Here is the summary with links:
  - [bpf,1/2] bpf: Restrict uprobe ctx writes to the registers ptrace can set
    https://git.kernel.org/bpf/bpf/c/ca44731a7009
  - [bpf,2/2] selftests/bpf: Test which ctx registers a uprobe prog can write
    https://git.kernel.org/bpf/bpf/c/c21b0f82ca96

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-20  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18  8:44 [PATCH bpf 0/2] bpf: Limit writable registers in uprobe context Jiri Olsa
2026-11-18  8:44 ` [PATCH bpf 1/2] bpf: Restrict uprobe ctx writes to the registers ptrace can set Jiri Olsa
2026-11-18  8:44 ` [PATCH bpf 2/2] selftests/bpf: Test which ctx registers a uprobe prog can write Jiri Olsa
2026-11-20  2:40 ` 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=179514240603.3989712.15825286425363086604.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mhiramat@kernel.org \
    --cc=oleg@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=rtm@csail.mit.edu \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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