tools/testing/selftests/net/packetdrill/tcp_syscall_bad_arg_syscall-invalid-buf-ptr.pkt

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/net/packetdrill/tcp_syscall_bad_arg_syscall-invalid-buf-ptr.pkt

Extension

.pkt

Size

893 bytes

Lines

26

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: syscall or user/kernel boundary

Status

core 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 participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.

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
// Test kernel behavior with NULL as buffer pointer

`./defaults.sh`

    0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
   +0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
   +0 fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
   +0 bind(3, ..., ...) = 0
   +0 listen(3, 1) = 0

   +0 < S 0:0(0) win 32792 <mss 1000,sackOK,nop,nop,nop,wscale 10>
   +0 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK,nop,wscale 8>
  +.2 < . 1:1(0) ack 1 win 514

   +0 accept(3, ..., ...) = 4

   +0 write(4, NULL, 1000) = -1 EFAULT (Bad address)
   +0 send(4, NULL, 1000, 0) = -1 EFAULT (Bad address)
   +0 sendto(4, NULL, 1000, 0, ..., ...) = -1 EFAULT (Bad address)

   +0 < . 1:1001(1000) ack 1 win 200
   +0 read(4, NULL, 1000) = -1 EFAULT (Bad address)
   +0 recv(4, NULL, 1000, 0) = -1 EFAULT (Bad address)
   +0 recvfrom(4, NULL, 1000, 0, ..., ...) = -1 EFAULT (Bad address)

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: core 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.