tools/testing/selftests/bpf/prog_tests/sock_create.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/prog_tests/sock_create.c

Extension

.c

Size

8229 bytes

Lines

349

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
• test_progs.h
• cgroup_helpers.h

Detected Declarations

• enum sock_create_test_error
• function load_prog
• function run_test
• function test_sock_create

Annotated Snippet

cgroup_fd = test__join_cgroup("/sock_create");
	if (!ASSERT_GE(cgroup_fd, 0, "join_cgroup"))
		return;

	for (i = 0; i < ARRAY_SIZE(tests); i++) {
		if (!test__start_subtest(tests[i].descr))
			continue;

		ASSERT_OK(run_test(cgroup_fd, &tests[i]), tests[i].descr);
	}

	close(cgroup_fd);
}

Annotation

• Immediate include surface: `linux/bpf.h`, `test_progs.h`, `cgroup_helpers.h`.
• Detected declarations: `enum sock_create_test_error`, `function load_prog`, `function run_test`, `function test_sock_create`.
• 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.