tools/testing/selftests/bpf/prog_tests/raw_tp_null.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/prog_tests/raw_tp_null.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/prog_tests/raw_tp_null.c- Extension
.c- Size
- 643 bytes
- Lines
- 29
- 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.hraw_tp_null.skel.hraw_tp_null_fail.skel.h
Detected Declarations
function test_raw_tp_null
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2024 Meta Platforms, Inc. and affiliates. */
#include <test_progs.h>
#include "raw_tp_null.skel.h"
#include "raw_tp_null_fail.skel.h"
void test_raw_tp_null(void)
{
struct raw_tp_null *skel;
RUN_TESTS(raw_tp_null_fail);
skel = raw_tp_null__open_and_load();
if (!ASSERT_OK_PTR(skel, "raw_tp_null__open_and_load"))
return;
skel->bss->tid = sys_gettid();
if (!ASSERT_OK(raw_tp_null__attach(skel), "raw_tp_null__attach"))
goto end;
ASSERT_OK(trigger_module_test_read(2), "trigger testmod read");
ASSERT_EQ(skel->bss->i, 3, "invocations");
end:
raw_tp_null__destroy(skel);
}
Annotation
- Immediate include surface: `test_progs.h`, `raw_tp_null.skel.h`, `raw_tp_null_fail.skel.h`.
- Detected declarations: `function test_raw_tp_null`.
- 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.