tools/testing/selftests/bpf/progs/raw_tp_null.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/raw_tp_null.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/raw_tp_null.c- Extension
.c- Size
- 791 bytes
- Lines
- 32
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
vmlinux.hbpf/bpf_tracing.hbpf_misc.h
Detected Declarations
function BPF_PROG
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2024 Meta Platforms, Inc. and affiliates. */
#include <vmlinux.h>
#include <bpf/bpf_tracing.h>
#include "bpf_misc.h"
char _license[] SEC("license") = "GPL";
int tid;
int i;
SEC("tp_btf/bpf_testmod_test_raw_tp_null_tp")
int BPF_PROG(test_raw_tp_null, struct sk_buff *skb)
{
struct task_struct *task = bpf_get_current_task_btf();
if (task->pid != tid)
return 0;
/* If dead code elimination kicks in, the increment +=2 will be
* removed. For raw_tp programs attaching to tracepoints in kernel
* modules, we mark input arguments as PTR_MAYBE_NULL, so branch
* prediction should never kick in.
*/
asm volatile ("%[i] += 1; if %[ctx] != 0 goto +1; %[i] += 2;"
: [i]"+r"(i)
: [ctx]"r"(skb)
: "memory");
return 0;
}
Annotation
- Immediate include surface: `vmlinux.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.