From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>, <bpf@vger.kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Martin KaFai Lau" <martin.lau@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Tejun Heo" <tj@kernel.org>,
"Dan Schatzberg" <dschatzberg@meta.com>, <kkd@meta.com>,
<kernel-team@meta.com>
Subject: Re: [PATCH bpf-next v1 4/4] selftests/bpf: Test modified syscall ctx for global subprog
Date: Tue, 17 Mar 2026 12:13:41 -0400 [thread overview]
Message-ID: <DH56VAB98LZ1.1AZSVSH14DOR3@etsalapatis.com> (raw)
In-Reply-To: <20260317111850.2107846-5-memxor@gmail.com>
On Tue Mar 17, 2026 at 7:18 AM EDT, Kumar Kartikeya Dwivedi wrote:
> Ensure that global subprogs can only accept an unmodified PTR_TO_CTX for
> syscall programs. For all other program types, fixed or variable offsets
> on PTR_TO_CTX is rejected when passed into an argument of any call
> instruction type, through the unified logic of check_func_arg_reg_off.
>
> Finally, add a positive example of a case that should succeed with all
> our previous changes.
>
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> ---
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
> .../bpf/progs/verifier_global_subprogs.c | 42 +++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/progs/verifier_global_subprogs.c b/tools/testing/selftests/bpf/progs/verifier_global_subprogs.c
> index 2250fc31574d..0c14adaddb90 100644
> --- a/tools/testing/selftests/bpf/progs/verifier_global_subprogs.c
> +++ b/tools/testing/selftests/bpf/progs/verifier_global_subprogs.c
> @@ -357,6 +357,48 @@ int arg_tag_ctx_syscall(void *ctx)
> return tracing_subprog_void(ctx) + tracing_subprog_u64(ctx) + tp_whatever(ctx);
> }
>
> +__weak int syscall_array_bpf_for(void *ctx __arg_ctx)
> +{
> + int *arr = ctx;
> + int i;
> +
> + bpf_for(i, 0, 100)
> + arr[i] *= i;
> +
> + return 0;
> +}
> +
> +SEC("?syscall")
> +__success __log_level(2)
> +int arg_tag_ctx_syscall_bpf_for(void *ctx)
> +{
> + return syscall_array_bpf_for(ctx);
> +}
> +
> +SEC("?syscall")
> +__failure __log_level(2)
> +__msg("arg#0 of syscall prog must have zero offset")
> +int arg_tag_ctx_syscall_fixed_off_bad(void *ctx)
> +{
> + char *p = ctx;
> +
> + p += 8;
> + return subprog_ctx_tag(p);
> +}
> +
> +SEC("?syscall")
> +__failure __log_level(2)
> +__msg("arg#0 of syscall prog must have zero offset")
> +int arg_tag_ctx_syscall_var_off_bad(void *ctx)
> +{
> + __u64 off = bpf_get_prandom_u32();
> + char *p = ctx;
> +
> + off &= 4;
> + p += off;
> + return subprog_ctx_tag(p);
> +}
> +
> __weak int subprog_dynptr(struct bpf_dynptr *dptr)
> {
> long *d, t, buf[1] = {};
prev parent reply other threads:[~2026-03-17 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 11:18 [PATCH bpf-next v1 0/4] Allow variable offsets for syscall PTR_TO_CTX Kumar Kartikeya Dwivedi
2026-03-17 11:18 ` [PATCH bpf-next v1 1/4] bpf: Support " Kumar Kartikeya Dwivedi
2026-03-17 12:09 ` bot+bpf-ci
2026-03-17 16:45 ` Emil Tsalapatis
2026-03-17 11:18 ` [PATCH bpf-next v1 2/4] selftests/bpf: Adjust syscall ctx variable offset tests Kumar Kartikeya Dwivedi
2026-03-17 18:24 ` Emil Tsalapatis
2026-03-17 11:18 ` [PATCH bpf-next v1 3/4] bpf: Reject modified syscall PTR_TO_CTX for global subprogs Kumar Kartikeya Dwivedi
2026-03-17 16:50 ` Emil Tsalapatis
2026-03-17 18:46 ` Kumar Kartikeya Dwivedi
2026-03-17 11:18 ` [PATCH bpf-next v1 4/4] selftests/bpf: Test modified syscall ctx for global subprog Kumar Kartikeya Dwivedi
2026-03-17 16:13 ` Emil Tsalapatis [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=DH56VAB98LZ1.1AZSVSH14DOR3@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dschatzberg@meta.com \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox