tools/testing/selftests/bpf/progs/verifier_default_trusted_ptr.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/verifier_default_trusted_ptr.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/verifier_default_trusted_ptr.c- Extension
.c- Size
- 707 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
vmlinux.hbpf/bpf_helpers.hbpf/bpf_tracing.hbpf_misc.h../test_kmods/bpf_testmod_kfunc.h
Detected Declarations
function __retval
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Copyright 2026 Google LLC.
*/
#include <vmlinux.h>
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_tracing.h>
#include "bpf_misc.h"
#include "../test_kmods/bpf_testmod_kfunc.h"
SEC("syscall")
__success __retval(0)
int test_default_trusted_ptr(void *ctx)
{
struct prog_test_member *trusted_ptr;
trusted_ptr = bpf_kfunc_get_default_trusted_ptr_test();
/*
* Test BPF kfunc bpf_get_default_trusted_ptr_test() returns a
* PTR_TO_BTF_ID | PTR_TRUSTED, therefore it should be accepted when
* passed to a BPF kfunc only accepting KF_TRUSTED_ARGS.
*/
bpf_kfunc_put_default_trusted_ptr_test(trusted_ptr);
return 0;
}
char _license[] SEC("license") = "GPL";
Annotation
- Immediate include surface: `vmlinux.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`, `bpf_misc.h`, `../test_kmods/bpf_testmod_kfunc.h`.
- Detected declarations: `function __retval`.
- 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.