lib/test_bpf.c

File Facts

System

Linux kernel

Corpus path

lib/test_bpf.c

Extension

.c

Size

376646 bytes

Lines

15935

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/module.h
• linux/filter.h
• linux/bpf.h
• linux/skbuff.h
• linux/netdevice.h
• linux/if_vlan.h
• linux/prandom.h
• linux/highmem.h
• linux/sched.h

Detected Declarations

• struct bpf_test
• struct skb_segment_test
• struct tail_call_test
• function bpf_fill_maxinsns1
• function bpf_fill_maxinsns2
• function bpf_fill_maxinsns3
• function bpf_fill_maxinsns4
• function bpf_fill_maxinsns5
• function bpf_fill_maxinsns6
• function bpf_fill_maxinsns7
• function bpf_fill_maxinsns8
• function bpf_fill_maxinsns9
• function bpf_fill_maxinsns10
• function __bpf_fill_ja
• function bpf_fill_maxinsns11
• function bpf_fill_maxinsns12
• function bpf_fill_maxinsns13
• function bpf_fill_ja
• function bpf_fill_ld_abs_get_processor_id
• function __bpf_fill_stxdw
• function bpf_fill_stxw
• function bpf_fill_stxdw
• function __bpf_ld_imm64
• function __bpf_fill_max_jmp
• function bpf_fill_max_jmp_taken_32
• function bpf_fill_max_jmp_taken
• function bpf_fill_max_jmp_not_taken_32
• function bpf_fill_max_jmp_not_taken
• function bpf_fill_max_jmp_always_taken_32
• function bpf_fill_max_jmp_always_taken
• function bpf_fill_max_jmp_never_taken_32
• function bpf_fill_max_jmp_never_taken
• function __bpf_alu_result
• function __bpf_fill_alu_shift
• function bpf_fill_alu64_lsh_imm
• function bpf_fill_alu64_rsh_imm
• function bpf_fill_alu64_arsh_imm
• function bpf_fill_alu64_lsh_reg
• function bpf_fill_alu64_rsh_reg
• function bpf_fill_alu64_arsh_reg
• function bpf_fill_alu32_lsh_imm
• function bpf_fill_alu32_rsh_imm
• function bpf_fill_alu32_arsh_imm
• function bpf_fill_alu32_lsh_reg
• function bpf_fill_alu32_rsh_reg
• function bpf_fill_alu32_arsh_reg
• function __bpf_fill_alu_shift_same_reg
• function bpf_fill_alu64_lsh_same_reg

Annotated Snippet

module_init(test_bpf_init);
module_exit(test_bpf_exit);

MODULE_DESCRIPTION("Testsuite for BPF interpreter and BPF JIT compiler");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/filter.h`, `linux/bpf.h`, `linux/skbuff.h`, `linux/netdevice.h`, `linux/if_vlan.h`, `linux/prandom.h`.
• Detected declarations: `struct bpf_test`, `struct skb_segment_test`, `struct tail_call_test`, `function bpf_fill_maxinsns1`, `function bpf_fill_maxinsns2`, `function bpf_fill_maxinsns3`, `function bpf_fill_maxinsns4`, `function bpf_fill_maxinsns5`, `function bpf_fill_maxinsns6`, `function bpf_fill_maxinsns7`.
• Atlas domain: Kernel Services / lib.
• Implementation status: integration 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.