tools/testing/selftests/bpf/test_kmods/bpf_test_no_cfi.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/test_kmods/bpf_test_no_cfi.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/test_kmods/bpf_test_no_cfi.c- Extension
.c- Size
- 1685 bytes
- Lines
- 85
- 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.hlinux/btf.hlinux/init.hlinux/module.h
Detected Declarations
struct bpf_test_no_cfi_opsfunction dummy_initfunction dummy_init_memberfunction dummy_regfunction dummy_unregfunction bpf_test_no_cfi_ops__fn_1function bpf_test_no_cfi_initfunction bpf_test_no_cfi_exitmodule init bpf_test_no_cfi_init
Annotated Snippet
module_init(bpf_test_no_cfi_init);
module_exit(bpf_test_no_cfi_exit);
MODULE_AUTHOR("Kuifeng Lee");
MODULE_DESCRIPTION("BPF no cfi_stubs test module");
MODULE_LICENSE("Dual BSD/GPL");
Annotation
- Immediate include surface: `linux/bpf.h`, `linux/btf.h`, `linux/init.h`, `linux/module.h`.
- Detected declarations: `struct bpf_test_no_cfi_ops`, `function dummy_init`, `function dummy_init_member`, `function dummy_reg`, `function dummy_unreg`, `function bpf_test_no_cfi_ops__fn_1`, `function bpf_test_no_cfi_init`, `function bpf_test_no_cfi_exit`, `module init bpf_test_no_cfi_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.