tools/testing/selftests/bpf/verifier/ld_dw.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/verifier/ld_dw.c

Extension

.c

Size

968 bytes

Lines

46

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

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

{
	"ld_dw: xor semi-random 64 bit imms, test 1",
	.insns = { },
	.data = { },
	.fill_helper = bpf_fill_rand_ld_dw,
	.prog_type = BPF_PROG_TYPE_SCHED_CLS,
	.result = ACCEPT,
	.retval = 4090,
},
{
	"ld_dw: xor semi-random 64 bit imms, test 2",
	.insns = { },
	.data = { },
	.fill_helper = bpf_fill_rand_ld_dw,
	.prog_type = BPF_PROG_TYPE_SCHED_CLS,
	.result = ACCEPT,
	.retval = 2047,
},
{
	"ld_dw: xor semi-random 64 bit imms, test 3",
	.insns = { },
	.data = { },
	.fill_helper = bpf_fill_rand_ld_dw,
	.prog_type = BPF_PROG_TYPE_SCHED_CLS,
	.result = ACCEPT,
	.retval = 511,
},
{
	"ld_dw: xor semi-random 64 bit imms, test 4",
	.insns = { },
	.data = { },
	.fill_helper = bpf_fill_rand_ld_dw,
	.prog_type = BPF_PROG_TYPE_SCHED_CLS,
	.result = ACCEPT,
	.retval = 5,
},
{
	"ld_dw: xor semi-random 64 bit imms, test 5",
	.insns = { },
	.data = { },
	.fill_helper = bpf_fill_rand_ld_dw,
	.prog_type = BPF_PROG_TYPE_SCHED_CLS,
	.result = ACCEPT,
	.retval = 1000000 - 6,
},

Annotation

• 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.