tools/testing/selftests/bpf/progs/verifier_may_goto_2.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/verifier_may_goto_2.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/verifier_may_goto_2.c- Extension
.c- Size
- 493 bytes
- Lines
- 29
- 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
bpf_misc.hbpf_experimental.h
Detected Declarations
function may_goto_c_code
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2025 Meta Platforms, Inc. and affiliates. */
#include "bpf_misc.h"
#include "bpf_experimental.h"
int gvar;
SEC("raw_tp")
__description("C code with may_goto 0")
__success
int may_goto_c_code(void)
{
int i, tmp[3];
for (i = 0; i < 3 && can_loop; i++)
tmp[i] = 0;
for (i = 0; i < 3 && can_loop; i++)
tmp[i] = gvar - i;
for (i = 0; i < 3 && can_loop; i++)
gvar += tmp[i];
return 0;
}
char _license[] SEC("license") = "GPL";
Annotation
- Immediate include surface: `bpf_misc.h`, `bpf_experimental.h`.
- Detected declarations: `function may_goto_c_code`.
- 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.