Open-coded task_vma iter
Subsystems (5)
v2 cover Open-coded task_vma iter
At Meta we have a profiling daemon which periodically collects information on many hosts. This collection usually involves grabbing stacks (user and kernel) using perf_event BPF progs and later symbolicating them. For user stacks we try to use BPF_F_USER_BUILD_ID and rely on remote symbolication, but BPF_F_USER_BUILD_ID doesn't always succeed. In those cases we must fall back to digging around in /proc/PID/maps to map virtual address to (binary, offset). The /proc/PID/maps digging does not occur synchronously with stack collection, so the process might already be gone, in which case it won't have /proc/PID/maps and we will fail to symbolicate.
This 'exited process problem' doesn't occur very often as most of the prod services we care to profile are long-lived daemons, but there are enough usecases to warrant a workaround: a BPF program which can be optionally loaded at data collection time and essentially walks /proc/PID/maps. Currently this is done by walking the vma list:
struct vm_area_struct* mmap = BPF_CORE_READ(mm, mmap); mmap_next = BPF_CORE_READ(rmap, vm_next); /* in a loop */
Since commit 763ecb035029 ("mm: remove the vma linked list") there's no longer a vma linked list to walk. Walking the vma maple tree is not as simple as hopping struct vm_area_struct->vm_next. Luckily,
commit f39af05949a4 ("mm: add VMA iterator"), another commit in that series, added struct vma_iterator and for_each_vma macro for easy vma iteration. If similar functionality was exposed to BPF programs, it would be perfect for our usecase.
This series adds such functionality, specifically a BPF equivalent of for_each_vma using the open-coded iterator style.
Notes:
* This approach was chosen after discussion on a previous series [0] which attempted to solve the same problem by adding a BPF_F_VMA_NEXT flag to bpf_find_vma.
* Unlike the task_vma bpf_iter, the open-coded iterator kfuncs here do not drop the vma read lock between iterations. See Alexei's response in [0].
* The [vsyscall] page isn't really part of task->mm's vmas, but /proc/PID/maps returns information about it anyways. The vma iter added here does not do the same. See comment on selftest in patch 3.
* bpf_iter_task_vma allocates a struct vma_iterator using BPF allocator and keeps a pointer to it. This is done in order to prevent changes to struct ma_state - which is wrapped by struct vma_iterator - from necessitating changes to uapi struct bpf_iter_task_vma.
Changelog:
v1 -> v2: https://lore.kernel.org/bpf/[email protected]/
* Patch 1
* Now removes the unnecessary BTF_TYPE_EMIT instead of changing the type (Yonghong)
* Patch 2
* Don't do unnecessary BTF_TYPE_EMIT (Yonghong)
* Bump task refcount to prevent ->mm reuse (Yonghong)
* Keep a pointer to vma_iterator in bpf_iter_task_vma, alloc/free via BPF mem allocator (Yonghong, Stanislav)
* Patch 3
Patch summary:
* Patch 1 is a tiny fix I ran into while implementing the vma iter in this series. It can be applied independently.
* Patch 2 is the meat of the implementation
* Patch 3 adds tests for the new functionality
* Existing iter tests exercise failure cases (e.g. prog that doesn't call _destroy()). I didn't replicate them in this series, but am happy to add them in v2 if folks feel that it would be worthwhile.
[0]: https://lore.kernel.org/bpf/[email protected]/
Dave Marchevsky (3):
bpf: Don't explicitly emit BTF for struct btf_iter_num
bpf: Introduce task_vma open-coded iterator kfuncs selftests/bpf: Add tests for open-coded task_vma iter
include/uapi/linux/bpf.h | 4 +
kernel/bpf/bpf_iter.c | 2 -
kernel/bpf/helpers.c | 3 +
kernel/bpf/task_iter.c | 79 +++++++++++++++++++
tools/include/uapi/linux/bpf.h | 5 ++
tools/lib/bpf/bpf_helpers.h | 8 ++
.../selftests/bpf/prog_tests/bpf_iter.c | 26 +++---
.../testing/selftests/bpf/prog_tests/iters.c | 71 +++++++++++++++++
...f_iter_task_vma.c => bpf_iter_task_vmas.c} | 0
.../selftests/bpf/progs/iters_task_vma.c | 56 +++++++++++++
10 files changed, 239 insertions(+), 15 deletions(-)
rename tools/testing/selftests/bpf/progs/{bpf_iter_task_vma.c => bpf_iter_task_vmas.c} (100%)
create mode 100644 tools/testing/selftests/bpf/progs/iters_task_vma.cSignature · 1 line
2.34.1
PATCH v2 1/3 bpf: Don't explicitly emit BTF for struct btf_iter_num
Commit 6018e1f407cc ("bpf: implement numbers iterator") added the BTF_TYPE_EMIT line that this patch is modifying. The struct btf_iter_num doesn't exist, so only a forward declaration is emitted in BTF:
FWD 'btf_iter_num' fwd_kind=struct
That commit was probably hoping to ensure that struct bpf_iter_num is emitted in vmlinux BTF. A previous version of this patch changed the line to emit the correct type, but Yonghong confirmed that it would definitely be emitted regardless in [0], so this patch simply removes the line.
This isn't marked "Fixes" because the extraneous btf_iter_num FWD wasn't causing any issues that I noticed, aside from mild confusion when I looked through the code.
[0]: https://lore.kernel.org/bpf/[email protected]/
--- kernel/bpf/bpf_iter.c | 2 -- 1 file changed, 2 deletions(-)
kernel/bpf/bpf_iter.c +0 -2
@@ -793,8 +793,6 @@ __bpf_kfunc int bpf_iter_num_new(struct bpf_iter_num *it, int start, int end)BUILD_BUG_ON (sizeof (struct bpf_iter_num_kern ) !=sizeof (struct bpf_iter_num ));BUILD_BUG_ON (__alignof__(struct bpf_iter_num_kern ) != __alignof__(struct bpf_iter_num )); -BTF_TYPE_EMIT (struct btf_iter_num ); -/* start == end is legit, it's an empty range and we'll just get NULL * on first (and any subsequent) bpf_iter_num_next() call */
Signature · 1 line
2.34.1
Re: [PATCH v2 bpf-next 1/3] bpf: Don't explicitly emit BTF for struct btf_iter_num
Quoted 12 lines · Dave Marchevsky
Commit
6018e1f407cc("bpf: implement numbers iterator") added theBTF_TYPE_EMITline that this patch is modifying. The structbtf_iter_numdoesn't exist, so only a forward declaration is emitted in BTF:FWD '
btf_iter_num' fwd_kind=structThat commit was probably hoping to ensure that struct
bpf_iter_numis emitted in vmlinux BTF. A previous version of this patch changed the line to emit the correct type, but Yonghong confirmed that it would definitely be emitted regardless in [0], so this patch simply removes the line.
Quoted 7 lines
This isn't marked "Fixes" because the extraneous
btf_iter_numFWD wasn't causing any issues that I noticed, aside from mild confusion when I looked through the code.[0]: https://lore.kernel.org/bpf/[email protected]/Signed-off-by Dave Marchevsky <[email protected]>
PATCH v2 2/3 bpf: Introduce task_vma open-coded iterator kfuncs
In reply to Dave MarchevskyThis patch adds kfuncs bpf_iter_task_vma_{new,next,destroy} which allow creation and manipulation of struct bpf_iter_task_vma in open-coded iterator style. BPF programs can use these kfuncs directly or through bpf_for_each macro for natural-looking iteration of all task vmas.
The implementation borrows heavily from bpf_find_vma helper's locking - differing only in that it holds the mmap_read lock for all iterations while the helper only executes its provided callback on a maximum of 1 vma. Aside from locking, struct vma_iterator and vma_next do all the heavy lifting.
The newly-added struct bpf_iter_task_vma has a name collision with a selftest for the seq_file task_vma iter's bpf skel, so the selftests/bpf/progs file is renamed in order to avoid the collision.
---
include/uapi/linux/bpf.h | 4 +
kernel/bpf/helpers.c | 3 +
kernel/bpf/task_iter.c | 79 +++++++++++++++++++
tools/include/uapi/linux/bpf.h | 5 ++
tools/lib/bpf/bpf_helpers.h | 8 ++
.../selftests/bpf/prog_tests/bpf_iter.c | 26 +++---
...f_iter_task_vma.c => bpf_iter_task_vmas.c} | 0
7 files changed, 112 insertions(+), 13 deletions(-)
rename tools/testing/selftests/bpf/progs/{bpf_iter_task_vma.c => bpf_iter_task_vmas.c} (100%)include/uapi/linux/bpf.h +4 -0
@@ -7291,4 +7291,8 @@ struct bpf_iter_num {__u64 __opaque[1 ]; } __attribute__((aligned(8))); +struct bpf_iter_task_vma { +__u64 __opaque[4 ];/* See bpf_iter_num comment above */ +} __attribute__((aligned (8 ))); +#endif /* _UAPI__LINUX_BPF_H__ */
kernel/bpf/helpers.c +3 -0
@@ -2482,6 +2482,9 @@ BTF_ID_FLAGS(func, bpf_dynptr_slice_rdwr, KF_RET_NULL) BTF_ID_FLAGS(func, bpf_iter_num_new, KF_ITER_NEW) BTF_ID_FLAGS(func, bpf_iter_num_next, KF_ITER_NEXT | KF_RET_NULL) BTF_ID_FLAGS(func, bpf_iter_num_destroy, KF_ITER_DESTROY) +BTF_ID_FLAGS(func, bpf_iter_task_vma_new, KF_ITER_NEW) +BTF_ID_FLAGS(func, bpf_iter_task_vma_next, KF_ITER_NEXT | KF_RET_NULL) +BTF_ID_FLAGS(func, bpf_iter_task_vma_destroy, KF_ITER_DESTROY) BTF_ID_FLAGS(func, bpf_dynptr_adjust) BTF_ID_FLAGS(func, bpf_dynptr_is_null)BTF_ID_FLAGS (func, bpf_dynptr_is_rdonly)
kernel/bpf/task_iter.c +79 -0
92 lines not on this page · raw message
tools/include/uapi/linux/bpf.h +5 -0
@@ -7291,4 +7291,9 @@ struct bpf_iter_num {__u64 __opaque[1 ]; } __attribute__((aligned(8))); +struct bpf_iter_task_vma { +__u64 __opaque[9 ];/* See bpf_iter_num comment above */ +char __opaque_c[3 ]; +} __attribute__((aligned (8 ))); +#endif /* _UAPI__LINUX_BPF_H__ */
tools/lib/bpf/bpf_helpers.h +8 -0
@@ -302,6 +302,14 @@ extern int bpf_iter_num_new(struct bpf_iter_num *it, int start, int end) __weakextern int *bpf_iter_num_next (struct bpf_iter_num *it)__weak __ksym; extern void bpf_iter_num_destroy(struct bpf_iter_num *it) __weak __ksym; +struct bpf_iter_task_vma ; + +extern int bpf_iter_task_vma_new(struct bpf_iter_task_vma *it, + struct task_struct *task, + unsigned long addr) __weak __ksym; +extern struct vm_area_struct *bpf_iter_task_vma_next (struct bpf_iter_task_vma *it)__weak __ksym; +extern void bpf_iter_task_vma_destroy(struct bpf_iter_task_vma *it) __weak __ksym; +#ifndef bpf_for_each/* bpf_for_each(iter_type, cur_elem, args...) provides generic construct for * using BPF open-coded iterators without having to write mundane explicit
tools/testing/selftests/bpf/prog_tests/bpf_iter.c +13 -13
@@ -10,7 +10,7 @@#include "bpf_iter_task.skel.h" #include "bpf_iter_task_stack.skel.h" #include "bpf_iter_task_file.skel.h" -#include "bpf_iter_task_vma.skel.h" +#include "bpf_iter_task_vmas.skel.h" #include "bpf_iter_task_btf.skel.h" #include "bpf_iter_tcp4.skel.h" #include "bpf_iter_tcp6.skel.h"
@@ -1399,19 +1399,19 @@ static void str_strip_first_line(char *str)static void test_task_vma_common (struct bpf_iter_attach_opts *opts) {int err, iter_fd =-1 , proc_maps_fd =-1 ; -struct bpf_iter_task_vma *skel; +struct bpf_iter_task_vmas *skel;int len, read_size =4 ;char maps_path[64 ]; - skel =bpf_iter_task_vma__open (); -if (!ASSERT_OK_PTR (skel,"bpf_iter_task_vma__open" )) + skel =bpf_iter_task_vmas__open (); +if (!ASSERT_OK_PTR (skel,"bpf_iter_task_vmas__open" ))return ; skel->bss->pid =getpid (); skel->bss->one_task = opts ?1 :0 ; - err =bpf_iter_task_vma__load (skel); -if (!ASSERT_OK (err,"bpf_iter_task_vma__load" )) + err =bpf_iter_task_vmas__load (skel); +if (!ASSERT_OK (err,"bpf_iter_task_vmas__load" )) goto out; skel->links.proc_maps = bpf_program__attach_iter(
@@ -1462,25 +1462,25 @@ static void test_task_vma_common(struct bpf_iter_attach_opts *opts) out:close (proc_maps_fd);close (iter_fd); -bpf_iter_task_vma__destroy (skel); +bpf_iter_task_vmas__destroy (skel); }static void test_task_vma_dead_task (void ) { -struct bpf_iter_task_vma *skel; +struct bpf_iter_task_vmas *skel;int wstatus, child_pid =-1 ;time_t start_tm, cur_tm;int err, iter_fd =-1 ;int wait_sec =3 ; - skel =bpf_iter_task_vma__open (); -if (!ASSERT_OK_PTR (skel,"bpf_iter_task_vma__open" )) + skel =bpf_iter_task_vmas__open (); +if (!ASSERT_OK_PTR (skel,"bpf_iter_task_vmas__open" ))return ; skel->bss->pid =getpid (); - err =bpf_iter_task_vma__load (skel); -if (!ASSERT_OK (err,"bpf_iter_task_vma__load" )) + err =bpf_iter_task_vmas__load (skel); +if (!ASSERT_OK (err,"bpf_iter_task_vmas__load" )) goto out; skel->links.proc_maps = bpf_program__attach_iter(
@@ -1533,7 +1533,7 @@ static void test_task_vma_dead_task(void) out:waitpid (child_pid, &wstatus,0 );close (iter_fd); -bpf_iter_task_vma__destroy (skel); +bpf_iter_task_vmas__destroy (skel); }void test_bpf_sockmap_map_iter_fd (void )
tools/testing/selftests/bpf/progs/bpf_iter_task_vmas.c renamed from tools/testing/selftests/bpf/progs/bpf_iter_task_vma.c +0 -0
Signature · 1 line
2.34.1
Re: [PATCH v2 bpf-next 2/3] bpf: Introduce task_vma open-coded iterator kfuncs
Quoted 15 lines · Dave Marchevsky
This patch adds kfuncs bpf_iter_task_vma_{new,next,destroy} which allow creation and manipulation of struct
bpf_iter_task_vmain open-coded iterator style. BPF programs can use these kfuncs directly or throughbpf_for_eachmacro for natural-looking iteration of all task vmas.The implementation borrows heavily from
bpf_find_vmahelper's locking - differing only in that it holds themmap_readlock for all iterations while the helper only executes its provided callback on a maximum of 1 vma. Aside from locking, structvma_iteratorandvma_nextdo all the heavy lifting.The newly-added struct
bpf_iter_task_vmahas a name collision with a selftest for theseq_filetask_vmaiter's bpf skel, so the selftests/bpf/progs file is renamed in order to avoid the collision.
Quoted 7 lines
Signed-off-by Dave Marchevsky <[email protected]>Cc Nathan Slingerland <[email protected]>--- include/uapi/linux/bpf.h | 4 + kernel/bpf/helpers.c | 3 + kernel/bpf/task_iter.c | 79 +++++++++++++++++++ tools/include/uapi/linux/bpf.h | 5 ++
I forgot to update the tools bpf.h to match
new changes in this respin.
will send v3 shortly doing so
Re: [PATCH v2 bpf-next 2/3] bpf: Introduce task_vma open-coded iterator kfuncs
In reply to Dave MarchevskyQuoted 102 lines · Dave Marchevsky
This patch adds kfuncs bpf_iter_task_vma_{new,next,destroy} which allow creation and manipulation of struct
bpf_iter_task_vmain open-coded iterator style. BPF programs can use these kfuncs directly or throughbpf_for_eachmacro for natural-looking iteration of all task vmas.The implementation borrows heavily from
bpf_find_vmahelper's locking - differing only in that it holds themmap_readlock for all iterations while the helper only executes its provided callback on a maximum of 1 vma. Aside from locking, structvma_iteratorandvma_nextdo all the heavy lifting.The newly-added struct
bpf_iter_task_vmahas a name collision with a selftest for theseq_filetask_vmaiter's bpf skel, so the selftests/bpf/progs file is renamed in order to avoid the collision.Signed-off-by Dave Marchevsky <[email protected]>Cc Nathan Slingerland <[email protected]>--- include/uapi/linux/bpf.h | 4 + kernel/bpf/helpers.c | 3 + kernel/bpf/task_iter.c | 79 +++++++++++++++++++ tools/include/uapi/linux/bpf.h | 5 ++ tools/lib/bpf/bpf_helpers.h | 8 ++ .../selftests/bpf/prog_tests/bpf_iter.c | 26 +++--- ...f_iter_task_vma.c => bpf_iter_task_vmas.c} | 0 7 files changed, 112 insertions(+), 13 deletions(-) rename tools/testing/selftests/bpf/progs/{bpf_iter_task_vma.c => bpf_iter_task_vmas.c} (100%)include/uapi/linux/bpf.h +4
-0@@ -7291,4 +7291,8 @@ struct bpf_iter_num {__u64 __opaque[1 ]; } __attribute__((aligned(8))); +struct bpf_iter_task_vma { +__u64 __opaque[4 ];/* See bpf_iter_num comment above */ +} __attribute__((aligned (8 ))); +#endif /* _UAPI__LINUX_BPF_H__ */ kernel/bpf/helpers.c +3
-0@@ -2482,6 +2482,9 @@ BTF_ID_FLAGS(func, bpf_dynptr_slice_rdwr, KF_RET_NULL) BTF_ID_FLAGS(func, bpf_iter_num_new, KF_ITER_NEW) BTF_ID_FLAGS(func, bpf_iter_num_next, KF_ITER_NEXT | KF_RET_NULL) BTF_ID_FLAGS(func, bpf_iter_num_destroy, KF_ITER_DESTROY) +BTF_ID_FLAGS(func, bpf_iter_task_vma_new, KF_ITER_NEW) +BTF_ID_FLAGS(func, bpf_iter_task_vma_next, KF_ITER_NEXT | KF_RET_NULL) +BTF_ID_FLAGS(func, bpf_iter_task_vma_destroy, KF_ITER_DESTROY) BTF_ID_FLAGS(func, bpf_dynptr_adjust) BTF_ID_FLAGS(func, bpf_dynptr_is_null)BTF_ID_FLAGS (func, bpf_dynptr_is_rdonly)kernel/bpf/task_iter.c +30
-0@@ -7,7 +7,9 @@#include <linux/fs.h> #include <linux/fdtable.h> #include <linux/filter.h> +#include <linux/bpf_mem_alloc.h> #include <linux/btf_ids.h> +#include <linux/mm_types.h> #include "mmap_unlock_work.h" static const char *const iter_task_type_names[] = {@@ -823,6 +825,83 @@ const struct bpf_func_proto bpf_find_vma_proto = { .arg5_type = ARG_ANYTHING, }; +/* Non-opaque version of uapi bpf_iter_task_vma */ +struct bpf_iter_task_vma_kern { +struct task_struct *task; +struct mm_struct *mm; +struct mmap_unlock_irq_work *work; +struct vma_iterator *vmi; +} __attribute__((aligned (8 ))); + +__bpf_kfunc int bpf_iter_task_vma_new(struct bpf_iter_task_vma *it, +struct task_struct *task,u64 addr) +{ +struct bpf_iter_task_vma_kern *kit = (void *)it; +bool irq_work_busy = false; +int err; + +BUILD_BUG_ON (sizeof (struct bpf_iter_task_vma_kern ) !=sizeof (struct bpf_iter_task_vma )); +BUILD_BUG_ON (__alignof__(struct bpf_iter_task_vma_kern ) != __alignof__(struct bpf_iter_task_vma )); + +/* NULL i->mm signals failed bpf_iter_task_vma initialization. +* i->work == NULL is valid. +*/ + kit->mm =NULL ; + kit->task =NULL ; +if (!task) +return -ENOENT ; + + kit->task =get_task_struct (task); + kit->mm = task->mm;
kernel/bpf/task_iter.c const struct bpf_func_proto bpf_find_vma_proto = { · line 865
Quoted 10 lines
kernel/bpf/task_iter.c +10
-0+if (!kit->mm) { + err = -ENOENT ; + goto err_put_task; + } + + kit->vmi =bpf_mem_alloc (&bpf_global_ma,sizeof (struct vma_iterator )); +if (!kit->vmi) { + err = -ENOMEM ; + goto err_put_task; + }
Since alloc is done anyway, let's alloc the whole bpf_iter_task_vma_kern and reduce bpf prog side to a single pointer?
PATCH v2 3/3 selftests/bpf: Add tests for open-coded task_vma iter
In reply to Dave MarchevskyThe open-coded task_vma iter added earlier in this series allows for natural iteration over a task's vmas using existing open-coded iter infrastructure, specifically bpf_for_each.
This patch adds a test demonstrating this pattern and validating correctness. The vma->vm_start and vma->vm_end addresses of the first 1000 vmas are recorded and compared to /proc/PID/maps output. As expected, both see the same vmas and addresses - with the exception of the [vsyscall] vma - which is explained in a comment in the prog_tests program.
--- .../testing/selftests/bpf/prog_tests/iters.c | 71 +++++++++++++++++++ .../selftests/bpf/progs/iters_task_vma.c | 56 +++++++++++++++ 2 files changed, 127 insertions(+) create mode 100644 tools/testing/selftests/bpf/progs/iters_task_vma.c
tools/testing/selftests/bpf/prog_tests/iters.c +71 -0
@@ -8,6 +8,7 @@#include "iters_looping.skel.h" #include "iters_num.skel.h" #include "iters_testmod_seq.skel.h" +#include "iters_task_vma.skel.h" static void subtest_num_iters (void ) {
@@ -90,6 +91,74 @@ static void subtest_testmod_seq_iters(void)iters_testmod_seq__destroy (skel); } +static void subtest_task_vma_iters (void ) +{ +unsigned long start, end, bpf_iter_start, bpf_iter_end; +struct iters_task_vma *skel; +char rest_of_line[1000 ]; +unsigned int seen; +int err; +FILE *f; + + skel =iters_task_vma__open (); +if (!ASSERT_OK_PTR (skel,"skel_open" )) +return ; + +bpf_program__set_autoload (skel->progs.iter_task_vma_for_each, true); + + err =iters_task_vma__load (skel); +if (!ASSERT_OK (err,"skel_load" )) + goto cleanup; + + skel->bss->target_pid =getpid (); + + err =iters_task_vma__attach (skel); +if (!ASSERT_OK (err,"skel_attach" )) + goto cleanup; + +iters_task_vma__detach (skel); +getpgid (skel->bss->target_pid); + +if (!ASSERT_GT (skel->bss->vmas_seen,0 ,"vmas_seen_gt_zero" )) + goto cleanup; + + f =fopen ("/proc/self/maps" ,"r" ); +if (!ASSERT_OK_PTR (f,"proc_maps_fopen" )) + goto cleanup; + + seen =0 ; +while (fscanf (f,"%lx-%lx %[^\n]\n" , &start, &end, rest_of_line) ==3 ) { +/* [vsyscall] vma isn't _really_ part of task->mm vmas. +* /proc/PID/maps returns it when out of vmas - see get_gate_vma +* calls in fs/proc/task_mmu.c +*/ +if (strstr (rest_of_line,"[vsyscall]" )) +continue ; + + err =bpf_map_lookup_elem (bpf_map__fd (skel->maps.vm_start), + &seen, &bpf_iter_start); +if (!ASSERT_OK (err,"vm_start map_lookup_elem" )) + goto cleanup; + + err =bpf_map_lookup_elem (bpf_map__fd (skel->maps.vm_end), + &seen, &bpf_iter_end); +if (!ASSERT_OK (err,"vm_end map_lookup_elem" )) + goto cleanup; + +ASSERT_EQ (bpf_iter_start, start,"vma->vm_start match" ); +ASSERT_EQ (bpf_iter_end, end,"vma->vm_end match" ); + seen++; + } + +fclose (f); + +if (!ASSERT_EQ (skel->bss->vmas_seen, seen,"vmas_seen_eq" )) + goto cleanup; + +cleanup: +iters_task_vma__destroy (skel); +} +void test_iters (void ) {RUN_TESTS (iters_state_safety);
@@ -103,4 +172,6 @@ void test_iters(void)subtest_num_iters ();if (test__start_subtest ("testmod_seq" ))subtest_testmod_seq_iters (); +if (test__start_subtest ("task_vma" )) +subtest_task_vma_iters (); }
tools/testing/selftests/bpf/progs/iters_task_vma.c new file +56 -0
56 lines not on this page · raw message
Signature · 1 line
2.34.1