tools/testing/selftests/bpf/test_kmods/bpf_test_modorder_y.c

Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/test_kmods/bpf_test_modorder_y.c

File Facts

System: Linux kernel
Corpus path: tools/testing/selftests/bpf/test_kmods/bpf_test_modorder_y.c
Extension: .c
Size: 877 bytes
Lines: 40
Domain: Support Tooling And Documentation
Bucket: tools
Inferred role: Support Tooling And Documentation: exported/initcall integration point
Status: integration 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.
Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/bpf.h
linux/btf.h
linux/module.h
linux/init.h

Detected Declarations

function bpf_test_modorder_rety
function bpf_test_modorder_y_init
function bpf_test_modorder_y_exit
module init bpf_test_modorder_y_init

Annotated Snippet

module_init(bpf_test_modorder_y_init);
module_exit(bpf_test_modorder_y_exit);

MODULE_DESCRIPTION("BPF selftest ordertest module Y");
MODULE_LICENSE("GPL");

Annotation

Immediate include surface: `linux/bpf.h`, `linux/btf.h`, `linux/module.h`, `linux/init.h`.
Detected declarations: `function bpf_test_modorder_rety`, `function bpf_test_modorder_y_init`, `function bpf_test_modorder_y_exit`, `module init bpf_test_modorder_y_init`.
Atlas domain: Support Tooling And Documentation / tools.
Implementation status: integration 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.