tools/testing/selftests/bpf/progs/struct_ops_autocreate.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/progs/struct_ops_autocreate.c

Extension

.c

Size

895 bytes

Lines

53

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

• linux/bpf.h
• bpf/bpf_helpers.h
• bpf/bpf_tracing.h

Detected Declarations

• struct bpf_testmod_ops___v1
• struct bpf_testmod_ops___v2
• function BPF_PROG
• function BPF_PROG

Annotated Snippet

struct bpf_testmod_ops___v1 {
	int (*test_1)(void);
};

struct bpf_testmod_ops___v2 {
	int (*test_1)(void);
	int (*does_not_exist)(void);
};

SEC(".struct_ops.link")
struct bpf_testmod_ops___v1 testmod_1 = {
	.test_1 = (void *)test_1
};

SEC(".struct_ops.link")
struct bpf_testmod_ops___v2 testmod_2 = {
	.test_1 = (void *)test_1,
	.does_not_exist = (void *)test_2
};

SEC("?.struct_ops")
struct bpf_testmod_ops___v1 optional_map = {
	.test_1 = (void *)test_1,
};

SEC("?.struct_ops.link")
struct bpf_testmod_ops___v1 optional_map2 = {
	.test_1 = (void *)test_1,
};

Annotation

• Immediate include surface: `linux/bpf.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`.
• Detected declarations: `struct bpf_testmod_ops___v1`, `struct bpf_testmod_ops___v2`, `function BPF_PROG`, `function BPF_PROG`.
• 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.