tools/testing/selftests/bpf/prog_tests/prog_array_init.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/prog_tests/prog_array_init.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/prog_tests/prog_array_init.c- Extension
.c- Size
- 766 bytes
- Lines
- 33
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
test_progs.htest_prog_array_init.skel.h
Detected Declarations
function test_prog_array_init
Annotated Snippet
#include <test_progs.h>
#include "test_prog_array_init.skel.h"
void test_prog_array_init(void)
{
struct test_prog_array_init *skel;
int err;
skel = test_prog_array_init__open();
if (!ASSERT_OK_PTR(skel, "could not open BPF object"))
return;
skel->rodata->my_pid = getpid();
err = test_prog_array_init__load(skel);
if (!ASSERT_OK(err, "could not load BPF object"))
goto cleanup;
skel->links.entry = bpf_program__attach_raw_tracepoint(skel->progs.entry, "sys_enter");
if (!ASSERT_OK_PTR(skel->links.entry, "could not attach BPF program"))
goto cleanup;
usleep(1);
ASSERT_EQ(skel->bss->value, 42, "unexpected value");
cleanup:
test_prog_array_init__destroy(skel);
}
Annotation
- Immediate include surface: `test_progs.h`, `test_prog_array_init.skel.h`.
- Detected declarations: `function test_prog_array_init`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.