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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

1612 bytes

Lines

65

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• vmlinux.h
• bpf/bpf_tracing.h
• bpf/bpf_helpers.h
• bpf/bpf_core_read.h
• bpf_misc.h
• bpf_experimental.h

Detected Declarations

• struct foo
• function __msg
• function __msg
• function __msg
• function __msg

Annotated Snippet

struct foo { int i; } *p;

	p = bpf_obj_new(typeof(*p));
	bpf_tail_call_static(ctx, &jmp_table, 0);
	return 0;
}

char _license[] SEC("license") = "GPL";

Annotation

• Immediate include surface: `vmlinux.h`, `bpf/bpf_tracing.h`, `bpf/bpf_helpers.h`, `bpf/bpf_core_read.h`, `bpf_misc.h`, `bpf_experimental.h`.
• Detected declarations: `struct foo`, `function __msg`, `function __msg`, `function __msg`, `function __msg`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.