tools/testing/selftests/bpf/prog_tests/autoattach.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/prog_tests/autoattach.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/prog_tests/autoattach.c- Extension
.c- Size
- 801 bytes
- Lines
- 31
- 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
test_progs.htest_autoattach.skel.h
Detected Declarations
function test_autoattach
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2022 Google */
#include <test_progs.h>
#include "test_autoattach.skel.h"
void test_autoattach(void)
{
struct test_autoattach *skel;
skel = test_autoattach__open_and_load();
if (!ASSERT_OK_PTR(skel, "skel_open_and_load"))
goto cleanup;
/* disable auto-attach for prog2 */
bpf_program__set_autoattach(skel->progs.prog2, false);
ASSERT_TRUE(bpf_program__autoattach(skel->progs.prog1), "autoattach_prog1");
ASSERT_FALSE(bpf_program__autoattach(skel->progs.prog2), "autoattach_prog2");
if (!ASSERT_OK(test_autoattach__attach(skel), "skel_attach"))
goto cleanup;
usleep(1);
ASSERT_TRUE(skel->bss->prog1_called, "attached_prog1");
ASSERT_FALSE(skel->bss->prog2_called, "attached_prog2");
cleanup:
test_autoattach__destroy(skel);
}
Annotation
- Immediate include surface: `test_progs.h`, `test_autoattach.skel.h`.
- Detected declarations: `function test_autoattach`.
- 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.