From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
Nicholas Carlini <npc@anthropic.com>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf-next v1 0/3] Fix acyclic ownership checks
Date: Sat, 5 Sep 2026 11:07:45 +0200 [thread overview]
Message-ID: <20260905090750.4064411-1-memxor@gmail.com> (raw)
Bound and ensure acyclic ownership graphs for native data structures to
fix a bug reported by Nicholas. See commit logs and tests for details.
Kumar Kartikeya Dwivedi (3):
bpf: Validate graph ownership with a bounded walk
bpf: Bound local kptr ownership depth
selftests/bpf: Check local object ownership depth
kernel/bpf/btf.c | 134 +++++++-----
.../selftests/bpf/prog_tests/linked_list.c | 4 +-
.../bpf/prog_tests/local_kptr_ownership.c | 202 ++++++++++++++++++
3 files changed, 290 insertions(+), 50 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/local_kptr_ownership.c
base-commit: 3ccdb07813829ba9487273e75d1cb238cfa774c1
--
2.53.0
next reply other threads:[~2026-09-05 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:07 Kumar Kartikeya Dwivedi [this message]
2026-09-05 9:07 ` [PATCH bpf-next v1 1/3] bpf: Validate graph ownership with a bounded walk Kumar Kartikeya Dwivedi
2026-09-05 21:29 ` Alexei Starovoitov
2026-09-05 9:07 ` [PATCH bpf-next v1 2/3] bpf: Bound local kptr ownership depth Kumar Kartikeya Dwivedi
2026-09-05 9:07 ` [PATCH bpf-next v1 3/3] selftests/bpf: Check local object " Kumar Kartikeya Dwivedi
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=20260905090750.4064411-1-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=npc@anthropic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.