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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

422 bytes

Lines

26

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• vmlinux.h
• bpf/bpf_helpers.h
• bpf/bpf_tracing.h

Detected Declarations

• function handle_kprobe_multi_sleepable
• function BPF_PROG

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0

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

void *user_ptr = 0;

SEC("kprobe.multi")
int handle_kprobe_multi_sleepable(struct pt_regs *ctx)
{
	int a, err;

	err = bpf_copy_from_user(&a, sizeof(a), user_ptr);
	barrier_var(a);
	return err;
}

SEC("fentry/bpf_fentry_test1")
int BPF_PROG(fentry)
{
	return 0;
}

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

Annotation

• Immediate include surface: `vmlinux.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`.
• Detected declarations: `function handle_kprobe_multi_sleepable`, `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.