tools/testing/selftests/bpf/prog_tests/uprobe.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/prog_tests/uprobe.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/prog_tests/uprobe.c- Extension
.c- Size
- 6086 bytes
- Lines
- 250
- 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.hasm/ptrace.htest_uprobe.skel.h
Detected Declarations
function urand_triggerfunction test_uprobe_attachfunction uprobe_regs_change_triggerfunction uprobe_regs_changefunction regs_commonfunction uprobe_regs_change_ip_1function uprobe_regs_change_ip_2function regs_ipfunction test_uprobe_regs_changefunction test_uprobe_regs_change
Annotated Snippet
static void test_uprobe_regs_change(void) { }
#endif
void test_uprobe(void)
{
if (test__start_subtest("attach"))
test_uprobe_attach();
test_uprobe_regs_change();
}Annotation
- Immediate include surface: `test_progs.h`, `asm/ptrace.h`, `test_uprobe.skel.h`.
- Detected declarations: `function urand_trigger`, `function test_uprobe_attach`, `function uprobe_regs_change_trigger`, `function uprobe_regs_change`, `function regs_common`, `function uprobe_regs_change_ip_1`, `function uprobe_regs_change_ip_2`, `function regs_ip`, `function test_uprobe_regs_change`, `function test_uprobe_regs_change`.
- 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.