From: Justin Suess <utilityemal77@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Cc: martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, bpf@vger.kernel.org, mic@digikod.net,
Justin Suess <utilityemal77@gmail.com>
Subject: [PATCH bpf-next 0/2] Allow storing referenced struct file kptrs in BPF maps
Date: Mon, 20 Apr 2026 16:33:04 -0400 [thread overview]
Message-ID: <20260420203306.3107246-1-utilityemal77@gmail.com> (raw)
Hello,
This series adds a destructor for struct file, enabling it to be used as a
referenced kptr in BPF maps.
The destructor mirrors bpf_put_file() semantics and releases the reference
via fput(). This allows pointers returned from kfuncs such as
bpf_get_task_exe_file() to be safely stored and later reused with helpers
and kfuncs that operate on struct file.
This fills a gap compared to bpf_dynptr_from_file(), where the resulting
dynptr can be stored in a map, but cannot be passed to kfuncs expecting
a struct file *.
Use cases include caching file references across events and deferring
processing while keeping the underlying file alive.
Patch 1 adds the struct file kptr destructor and wires it into the BTF
kfunc sets.
Patch 2 adds selftests covering successful use and verifier rejection of
unreferenced pointers.
Justin Suess (2):
bpf: Implement dtor for struct file BTF ID
selftests/bpf: Add test for map-stored struct file kptrs
kernel/bpf/helpers.c | 16 +-
.../bpf/prog_tests/refcounted_kptr_file.c | 246 ++++++++++++++++++
.../bpf/progs/refcounted_kptr_file.c | 152 +++++++++++
.../bpf/progs/refcounted_kptr_file_fail.c | 35 +++
4 files changed, 448 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/refcounted_kptr_file.c
create mode 100644 tools/testing/selftests/bpf/progs/refcounted_kptr_file.c
create mode 100644 tools/testing/selftests/bpf/progs/refcounted_kptr_file_fail.c
--
2.53.0
next reply other threads:[~2026-04-20 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 20:33 Justin Suess [this message]
2026-04-20 20:33 ` [PATCH bpf-next 1/2] bpf: Implement dtor for struct file BTF ID Justin Suess
2026-04-20 22:17 ` Song Liu
2026-04-21 1:05 ` sashiko-bot
2026-04-21 2:18 ` Justin Suess
2026-04-21 19:38 ` Justin Suess
2026-04-21 20:29 ` Kumar Kartikeya Dwivedi
2026-04-20 20:33 ` [PATCH bpf-next 2/2] selftests/bpf: Add test for map-stored struct file kptrs Justin Suess
2026-04-20 21:07 ` bot+bpf-ci
2026-04-20 22:28 ` Song Liu
2026-04-21 1:31 ` sashiko-bot
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=20260420203306.3107246-1-utilityemal77@gmail.com \
--to=utilityemal77@gmail.com \
--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=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mic@digikod.net \
--cc=song@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