From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: alexei.starovoitov@gmail.com, andrii@kernel.org,
martin.lau@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
eddyz87@gmail.com, ameryhung@gmail.com, kernel-team@meta.com
Subject: [PATCH bpf-next v1 0/2] Allow referenced dynptr to be overwritten when siblings exists
Date: Mon, 6 Apr 2026 08:05:46 -0700 [thread overview]
Message-ID: <20260406150548.1354271-1-ameryhung@gmail.com> (raw)
The patchset conditionally allow a referenced dynptr to be overwritten
when its siblings (original dynptr or dynptr clone) exist. Do it before
the verifier relation tracking refactor to mimimize verifier changes at
a time.
Amery Hung (2):
bpf: Allow overwriting referenced dynptr when refcnt > 1
selftests/bpf: Test overwriting referenced dynptr
kernel/bpf/verifier.c | 23 +++-
.../testing/selftests/bpf/progs/dynptr_fail.c | 115 ++++++++++++++++++
2 files changed, 136 insertions(+), 2 deletions(-)
--
2.52.0
next reply other threads:[~2026-04-06 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 15:05 Amery Hung [this message]
2026-04-06 15:05 ` [PATCH bpf-next v1 1/2] bpf: Allow overwriting referenced dynptr when refcnt > 1 Amery Hung
2026-04-07 15:51 ` Kumar Kartikeya Dwivedi
2026-04-07 21:27 ` Alexei Starovoitov
2026-04-07 22:05 ` Amery Hung
2026-04-07 22:13 ` Kumar Kartikeya Dwivedi
2026-04-06 15:05 ` [PATCH bpf-next v1 2/2] selftests/bpf: Test overwriting referenced dynptr Amery Hung
2026-04-07 15:58 ` Kumar Kartikeya Dwivedi
2026-04-08 1:30 ` [PATCH bpf-next v1 0/2] Allow referenced dynptr to be overwritten when siblings exists patchwork-bot+netdevbpf
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=20260406150548.1354271-1-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 \
/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