tools/testing/selftests/bpf/progs/test_signed_loader.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/test_signed_loader.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/test_signed_loader.c- Extension
.c- Size
- 574 bytes
- Lines
- 19
- 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.
Dependency Surface
vmlinux.hbpf/bpf_helpers.h
Detected Declarations
function probe
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include "vmlinux.h"
#include <bpf/bpf_helpers.h>
/*
* Minimal, map-less program. Driven through libbpf's gen_loader (gen_hash)
* by prog_tests/signed_loader.c so the generated light-skeleton loader (with
* the emit_signature_match metadata check) can be exercised against good
* and tampered metadata. A socket filter needs no load-time attach resolution,
* and having no maps keeps the generated loader's ctx trivial (0 maps, 1 prog).
*/
SEC("socket")
int probe(void *ctx)
{
return 0;
}
char _license[] SEC("license") = "GPL";
Annotation
- Immediate include surface: `vmlinux.h`, `bpf/bpf_helpers.h`.
- Detected declarations: `function probe`.
- 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.