tools/testing/selftests/net/netfilter/connect_close.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/net/netfilter/connect_close.c

Extension

.c

Size

2071 bytes

Lines

137

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

• stdio.h
• stdlib.h
• fcntl.h
• string.h
• unistd.h
• signal.h
• arpa/inet.h
• sys/socket.h

Detected Declarations

• function handler
• function set_timeout
• function do_connect
• function do_accept
• function accept_loop
• function connect_loop
• function parse_opts
• function main

Annotated Snippet

switch (c) {
		case 't':
			opts.timeout = atoi(optarg);
			break;
		case 'p':
			opts.port = atoi(optarg);
			break;
		}
	}
}

int main(int argc, char *argv[])
{
	pid_t p;

	parse_opts(argc, argv);

	p = fork();
	if (p < 0)
		return 111;

	if (p > 0)
		return accept_loop();

	return connect_loop();
}

Annotation

• Immediate include surface: `stdio.h`, `stdlib.h`, `fcntl.h`, `string.h`, `unistd.h`, `signal.h`, `arpa/inet.h`, `sys/socket.h`.
• Detected declarations: `function handler`, `function set_timeout`, `function do_connect`, `function do_accept`, `function accept_loop`, `function connect_loop`, `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.