From: Song Liu <song@kernel.org>
To: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Cc: kernel-team@meta.com, andrii@kernel.org, eddyz87@gmail.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
kpsingh@kernel.org, mattbobrowski@google.com, amir73il@gmail.com,
repnop@google.com, jlayton@kernel.org, josef@toxicpanda.com,
mic@digikod.net, gnoack@google.com, m@maowtm.org,
Song Liu <song@kernel.org>
Subject: [PATCH v2 bpf-next 4/4] selftests/bpf: Add tests for bpf path iterator
Date: Mon, 2 Jun 2025 23:59:20 -0700 [thread overview]
Message-ID: <20250603065920.3404510-5-song@kernel.org> (raw)
In-Reply-To: <20250603065920.3404510-1-song@kernel.org>
Add tests for bpf path iterator, including test cases similar to real
workload (call bpf_path_d_path and bpf_get_dentry_xattr), and test cases
where the verifier rejects invalid use of the iterator.
Signed-off-by: Song Liu <song@kernel.org>
---
.../testing/selftests/bpf/bpf_experimental.h | 6 +
.../selftests/bpf/prog_tests/path_iter.c | 12 ++
tools/testing/selftests/bpf/progs/path_iter.c | 134 ++++++++++++++++++
3 files changed, 152 insertions(+)
create mode 100644 tools/testing/selftests/bpf/prog_tests/path_iter.c
create mode 100644 tools/testing/selftests/bpf/progs/path_iter.c
diff --git a/tools/testing/selftests/bpf/bpf_experimental.h b/tools/testing/selftests/bpf/bpf_experimental.h
index 5e512a1d09d1..cbb759b473df 100644
--- a/tools/testing/selftests/bpf/bpf_experimental.h
+++ b/tools/testing/selftests/bpf/bpf_experimental.h
@@ -596,4 +596,10 @@ extern int bpf_iter_dmabuf_new(struct bpf_iter_dmabuf *it) __weak __ksym;
extern struct dma_buf *bpf_iter_dmabuf_next(struct bpf_iter_dmabuf *it) __weak __ksym;
extern void bpf_iter_dmabuf_destroy(struct bpf_iter_dmabuf *it) __weak __ksym;
+struct bpf_iter_path;
+extern int bpf_iter_path_new(struct bpf_iter_path *it, struct path *start,
+ __u64 flags) __weak __ksym;
+extern struct path *bpf_iter_path_next(struct bpf_iter_path *it) __weak __ksym;
+extern void bpf_iter_path_destroy(struct bpf_iter_path *it) __weak __ksym;
+
#endif
diff --git a/tools/testing/selftests/bpf/prog_tests/path_iter.c b/tools/testing/selftests/bpf/prog_tests/path_iter.c
new file mode 100644
index 000000000000..3c99c24fbd96
--- /dev/null
+++ b/tools/testing/selftests/bpf/prog_tests/path_iter.c
@@ -0,0 +1,12 @@
+// SPDX-License-Identifier: GPL-2.0
+/* Copyright (c) 2025 Meta Platforms, Inc. and affiliates. */
+
+#include <test_progs.h>
+#include <bpf/libbpf.h>
+#include <bpf/btf.h>
+#include "path_iter.skel.h"
+
+void test_path_iter(void)
+{
+ RUN_TESTS(path_iter);
+}
diff --git a/tools/testing/selftests/bpf/progs/path_iter.c b/tools/testing/selftests/bpf/progs/path_iter.c
new file mode 100644
index 000000000000..be804fb4302c
--- /dev/null
+++ b/tools/testing/selftests/bpf/progs/path_iter.c
@@ -0,0 +1,134 @@
+// SPDX-License-Identifier: GPL-2.0
+/* Copyright (c) 2025 Meta Platforms, Inc. and affiliates. */
+
+#include "vmlinux.h"
+#include <bpf/bpf_helpers.h>
+#include <bpf/bpf_tracing.h>
+#include "bpf_misc.h"
+#include "bpf_experimental.h"
+
+char _license[] SEC("license") = "GPL";
+
+char path_name[256];
+char xattr_val[64];
+
+static __always_inline void access_path_dentry(struct path *p)
+{
+ struct bpf_dynptr ptr;
+ struct dentry *dentry;
+
+ if (!p)
+ return;
+
+ bpf_dynptr_from_mem(xattr_val, sizeof(xattr_val), 0, &ptr);
+ bpf_path_d_path(p, path_name, sizeof(path_name));
+
+ dentry = p->dentry;
+ if (dentry)
+ bpf_get_dentry_xattr(dentry, "user.xattr", &ptr);
+}
+
+SEC("lsm.s/file_open")
+__success
+int BPF_PROG(open_code, struct file *f)
+{
+ struct bpf_iter_path path_it;
+ struct path *p;
+ int ret;
+
+ ret = bpf_iter_path_new(&path_it, &f->f_path, 0);
+ if (ret) {
+ bpf_iter_path_destroy(&path_it);
+ return 0;
+ }
+
+ p = bpf_iter_path_next(&path_it);
+ access_path_dentry(p);
+ bpf_iter_path_destroy(&path_it);
+
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__success
+int BPF_PROG(for_each, struct file *f)
+{
+ struct path *p;
+
+ bpf_for_each(path, p, &f->f_path, 0)
+ access_path_dentry(p);
+
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__failure __msg("Unreleased reference")
+int BPF_PROG(missing_destroy, struct file *f)
+{
+ struct bpf_iter_path path_it;
+
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__failure __msg("expected an initialized iter_path")
+int BPF_PROG(missing_new, struct file *f)
+{
+ struct bpf_iter_path path_it;
+
+ bpf_iter_path_destroy(&path_it);
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__failure __msg("expected uninitialized iter_path")
+int BPF_PROG(new_twice, struct file *f)
+{
+ struct bpf_iter_path path_it;
+
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ bpf_iter_path_destroy(&path_it);
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__failure __msg("expected an initialized iter_path")
+int BPF_PROG(destroy_twice, struct file *f)
+{
+ struct bpf_iter_path path_it;
+
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ bpf_iter_path_destroy(&path_it);
+ bpf_iter_path_destroy(&path_it);
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__success
+int BPF_PROG(reuse_path_iter, struct file *f)
+{
+ struct bpf_iter_path path_it;
+
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ bpf_iter_path_destroy(&path_it);
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ bpf_iter_path_destroy(&path_it);
+ return 0;
+}
+
+SEC("lsm.s/file_open")
+__failure __msg("invalid read from stack off")
+int BPF_PROG(invalid_read_path_iter, struct file *f)
+{
+ struct bpf_iter_path path_it;
+ struct bpf_iter_path path_it_2;
+
+
+ bpf_iter_path_new(&path_it, &f->f_path, 0);
+ path_it_2 = path_it;
+ bpf_iter_path_destroy(&path_it_2);
+ return 0;
+}
--
2.47.1
prev parent reply other threads:[~2025-06-03 6:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 6:59 [PATCH v2 bpf-next 0/4] bpf path iterator Song Liu
2025-06-03 6:59 ` [PATCH v2 bpf-next 1/4] namei: Introduce new helper function path_walk_parent() Song Liu
2025-06-06 11:10 ` Mickaël Salaün
2025-06-06 14:40 ` Al Viro
2025-06-06 17:01 ` Song Liu
2025-06-03 6:59 ` [PATCH v2 bpf-next 2/4] landlock: Use path_walk_parent() Song Liu
2025-06-03 13:46 ` Mickaël Salaün
2025-06-04 19:37 ` Song Liu
2025-06-05 16:47 ` Song Liu
2025-06-06 10:46 ` Mickaël Salaün
2025-06-03 6:59 ` [PATCH v2 bpf-next 3/4] bpf: Introduce path iterator Song Liu
2025-06-03 15:13 ` Alexei Starovoitov
2025-06-04 17:22 ` Christian Brauner
2025-06-03 18:40 ` Andrii Nakryiko
2025-06-03 20:49 ` Yonghong Song
2025-06-03 21:10 ` Song Liu
2025-06-03 21:09 ` Song Liu
2025-06-03 21:44 ` Andrii Nakryiko
2025-06-03 23:20 ` Song Liu
2025-06-04 20:37 ` Andrii Nakryiko
2025-06-05 19:27 ` Matt Bobrowski
2025-06-05 21:14 ` Song Liu
2025-06-03 6:59 ` Song Liu [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=20250603065920.3404510-5-song@kernel.org \
--to=song@kernel.org \
--cc=amir73il@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=gnoack@google.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m@maowtm.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=mic@digikod.net \
--cc=repnop@google.com \
--cc=viro@zeniv.linux.org.uk \
/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.