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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

723 bytes

Lines

35

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

• linux/bpf.h
• errno.h
• bpf/bpf_helpers.h
• bpf/bpf_tracing.h

Detected Declarations

• function BPF_PROG

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0

/*
 * Copyright 2020 Google LLC.
 */

#include <linux/bpf.h>
#include <errno.h>
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_tracing.h>

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

struct {
	__uint(type, BPF_MAP_TYPE_TASK_STORAGE);
	__uint(map_flags, BPF_F_NO_PREALLOC);
	__type(key, int);
	__type(value, int);
} secure_exec_task_map SEC(".maps");

SEC("lsm/bprm_creds_for_exec")
int BPF_PROG(secure_exec, struct linux_binprm *bprm)
{
	int *secureexec;

	secureexec = bpf_task_storage_get(&secure_exec_task_map,
				   bpf_get_current_task_btf(), 0,
				   BPF_LOCAL_STORAGE_GET_F_CREATE);

	if (secureexec && *secureexec)
		bpf_bprm_opts_set(bprm, BPF_F_BPRM_SECUREEXEC);

	return 0;
}

Annotation

• Immediate include surface: `linux/bpf.h`, `errno.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.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.