tools/testing/selftests/net/packetdrill/tcp_basic_client.pkt

Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/packetdrill/tcp_basic_client.pkt

File Facts

System: Linux kernel
Corpus path: tools/testing/selftests/net/packetdrill/tcp_basic_client.pkt
Extension: .pkt
Size: 642 bytes
Lines: 25
Domain: Support Tooling And Documentation
Bucket: tools
Inferred role: Support Tooling And Documentation: tools
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
//
// Minimal active open.
// First to close connection.

`./defaults.sh`

    0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 4

   // Connect to server: active open: three-way handshake
   +0...0 connect(4, ..., ...) = 0
   +0 > S 0:0(0) <mss 1460,sackOK,TS val 0 ecr 0,nop,wscale 8>
   +0 < S. 0:0(0) ack 1 win 65535 <mss 1460,sackOK,nop,nop,nop,wscale 7>
   +0 > . 1:1(0) ack 1

   // Send data
   +0 send(4, ..., 1000, 0) = 1000
   +0 > P. 1:1001(1000) ack 1
   +0 < . 1:1(0) ack 1001 win 257

   +0 close(4) = 0
   +0 > F. 1001:1001(0) ack 1
   +0 < F. 1:1(0) ack 1002 win 257
   +0 > . 1002:1002(0) ack 2

Annotation

Atlas domain: Support Tooling And Documentation / tools.
Implementation status: atlas-only.

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.