tools/testing/selftests/bpf/progs/verifier_mul.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/verifier_mul.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/verifier_mul.c- Extension
.c- Size
- 1011 bytes
- Lines
- 39
- 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
linux/bpf.hbpf/bpf_helpers.hbpf/bpf_tracing.hbpf_misc.h
Detected Declarations
function BPF_PROG
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2025 Nandakumar Edamana */
#include <linux/bpf.h>
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_tracing.h>
#include "bpf_misc.h"
/* Intended to test the abstract multiplication technique(s) used by
* the verifier. Using assembly to avoid compiler optimizations.
*/
SEC("fentry/bpf_fentry_test1")
void BPF_PROG(mul_precise, int x)
{
/* First, force the verifier to be uncertain about the value:
* unsigned int a = (bpf_get_prandom_u32() & 0x2) | 0x1;
*
* Assuming the verifier is using tnum, a must be tnum{.v=0x1, .m=0x2}.
* Then a * 0x3 would be m0m1 (m for uncertain). Added imprecision
* would cause the following to fail, because the required return value
* is 0:
* return (a * 0x3) & 0x4);
*/
asm volatile ("\
call %[bpf_get_prandom_u32];\
r0 &= 0x2;\
r0 |= 0x1;\
r0 *= 0x3;\
r0 &= 0x4;\
if r0 != 0 goto l0_%=;\
r0 = 0;\
goto l1_%=;\
l0_%=:\
r0 = 1;\
l1_%=:\
" :
: __imm(bpf_get_prandom_u32)
: __clobber_all);
}
Annotation
- Immediate include surface: `linux/bpf.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`, `bpf_misc.h`.
- Detected declarations: `function BPF_PROG`.
- 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.