tools/testing/selftests/bpf/progs/test_ptr_untrusted.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/progs/test_ptr_untrusted.c

Extension

.c

Size

561 bytes

Lines

30

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.

Dependency Surface

• vmlinux.h
• bpf/bpf_tracing.h

Detected Declarations

• function BPF_PROG
• function BPF_PROG

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
/* Copyright (C) 2023 Yafang Shao <laoar.shao@gmail.com> */

#include "vmlinux.h"
#include <bpf/bpf_tracing.h>

char tp_name[128];

SEC("lsm.s/bpf")
int BPF_PROG(lsm_run, int cmd, union bpf_attr *attr, unsigned int size, bool kernel)
{
	switch (cmd) {
	case BPF_RAW_TRACEPOINT_OPEN:
		bpf_copy_from_user(tp_name, sizeof(tp_name) - 1,
				   (void *)attr->raw_tracepoint.name);
		break;
	default:
		break;
	}
	return 0;
}

SEC("raw_tracepoint")
int BPF_PROG(raw_tp_run)
{
	return 0;
}

char _license[] SEC("license") = "GPL";

Annotation

• Immediate include surface: `vmlinux.h`, `bpf/bpf_tracing.h`.
• Detected declarations: `function BPF_PROG`, `function BPF_PROG`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.