Netdev List
 help / color / mirror / Atom feed
From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
	andrii@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
	memxor@gmail.com, martin.lau@kernel.org,
	mykyta.yatsenko5@gmail.com, ameryhung@gmail.com,
	kernel-team@meta.com
Subject: [PATCH bpf-next v6 03/13] bpf: Assign reg->id when getting referenced kptr from ctx
Date: Thu, 28 May 2026 18:49:26 -0700	[thread overview]
Message-ID: <20260529014936.2811085-4-ameryhung@gmail.com> (raw)
In-Reply-To: <20260529014936.2811085-1-ameryhung@gmail.com>

Assign reg->id when getting referenced kptr from read program context
to be consistent with R0 of KF_ACQUIRE kfunc. skb dynptr will track the
referenced skb in qdisc programs using a new field reg->parent_id in
a later patch.

Acked-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
Signed-off-by: Amery Hung <ameryhung@gmail.com>
---
 kernel/bpf/verifier.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index d29846c4998a..552840d8d2bd 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -6208,8 +6208,6 @@ static int check_mem_access(struct bpf_verifier_env *env, int insn_idx, struct b
 			} else {
 				mark_reg_known_zero(env, regs,
 						    value_regno);
-				if (type_may_be_null(info.reg_type))
-					regs[value_regno].id = ++env->id_gen;
 				/* A load of ctx field could have different
 				 * actual load size with the one encoded in the
 				 * insn. When the dst is PTR, it is for sure not
@@ -6219,8 +6217,11 @@ static int check_mem_access(struct bpf_verifier_env *env, int insn_idx, struct b
 				if (base_type(info.reg_type) == PTR_TO_BTF_ID) {
 					regs[value_regno].btf = info.btf;
 					regs[value_regno].btf_id = info.btf_id;
+					regs[value_regno].id = info.ref_obj_id;
 					regs[value_regno].ref_obj_id = info.ref_obj_id;
 				}
+				if (type_may_be_null(info.reg_type) && !regs[value_regno].id)
+					regs[value_regno].id = ++env->id_gen;
 			}
 			regs[value_regno].type = info.reg_type;
 		}
-- 
2.53.0-Meta


  parent reply	other threads:[~2026-05-29  1:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  1:49 [PATCH bpf-next v6 00/13] Refactor verifier object relationship tracking Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 01/13] bpf: Simplify mark_stack_slot_obj_read() and callers Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 02/13] bpf: Unify dynptr handling in the verifier Amery Hung
2026-05-29  2:39   ` bot+bpf-ci
2026-05-29  1:49 ` Amery Hung [this message]
2026-05-29  1:49 ` [PATCH bpf-next v6 04/13] bpf: Preserve reg->id of pointer objects after null-check Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 05/13] bpf: Refactor object relationship tracking and fix dynptr UAF bug Amery Hung
2026-05-29  2:54   ` bot+bpf-ci
2026-05-29  1:49 ` [PATCH bpf-next v6 06/13] bpf: Remove redundant dynptr arg check for helper Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 07/13] bpf: Unify referenced object tracking in verifier Amery Hung
2026-05-29  2:40   ` bot+bpf-ci
2026-05-29  1:49 ` [PATCH bpf-next v6 08/13] bpf: Unify release handling for helpers and kfuncs Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 09/13] bpf: Fix dynptr ref counting to scan all call frames Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 10/13] selftests/bpf: Test creating dynptr from dynptr data and slice Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 11/13] selftests/bpf: Test using slice after invalidating dynptr clone Amery Hung
2026-05-29  2:39   ` bot+bpf-ci
2026-05-29  1:49 ` [PATCH bpf-next v6 12/13] selftests/bpf: Test using file dynptr after the reference on file is dropped Amery Hung
2026-05-29  1:49 ` [PATCH bpf-next v6 13/13] selftests/bpf: Test using dynptr after freeing the underlying object Amery Hung

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=20260529014936.2811085-4-ameryhung@gmail.com \
    --to=ameryhung@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox