tools/testing/selftests/net/ipv6_flowlabel_mgr.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/net/ipv6_flowlabel_mgr.c

Extension

.c

Size

5506 bytes

Lines

200

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

• arpa/inet.h
• error.h
• errno.h
• limits.h
• linux/in6.h
• stdbool.h
• stdio.h
• stdint.h
• stdlib.h
• string.h
• sys/socket.h
• sys/stat.h
• sys/time.h
• sys/types.h
• sys/wait.h
• unistd.h

Detected Declarations

• function flowlabel_get
• function flowlabel_put
• function run_tests
• function parse_opts
• function main

Annotated Snippet

switch (c) {
		case 'l':
			cfg_long_running = true;
			break;
		case 'v':
			cfg_verbose = true;
			break;
		default:
			error(1, 0, "%s: parse error", argv[0]);
		}
	}
}

int main(int argc, char **argv)
{
	int fd;

	parse_opts(argc, argv);

	fd = socket(PF_INET6, SOCK_DGRAM, 0);
	if (fd == -1)
		error(1, errno, "socket");

	run_tests(fd);

	if (close(fd))
		error(1, errno, "close");

	return 0;
}

Annotation

• Immediate include surface: `arpa/inet.h`, `error.h`, `errno.h`, `limits.h`, `linux/in6.h`, `stdbool.h`, `stdio.h`, `stdint.h`.
• Detected declarations: `function flowlabel_get`, `function flowlabel_put`, `function run_tests`, `function parse_opts`, `function main`.
• 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.