tools/testing/selftests/net/ipv6_fragmentation.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/ipv6_fragmentation.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/net/ipv6_fragmentation.c- Extension
.c- Size
- 3021 bytes
- Lines
- 115
- 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
error.hnet/if.hnetinet/in.hsched.hstdio.hsys/ioctl.hsys/socket.hunistd.hkselftest.h
Detected Declarations
function localhostfunction main
Annotated Snippet
if (errno == EADDRNOTAVAIL) {
usleep(1000);
goto send_again;
}
error(KSFT_FAIL, errno, "sendmsg");
} else if (rc != LARGER_THAN_MTU) {
error(KSFT_FAIL, errno, "sendmsg returned %zi, expected %i",
rc, LARGER_THAN_MTU);
}
printf("[PASS] sendmsg() returned %zi\n", rc);
if (close(s) == -1)
error(KSFT_FAIL, errno, "close");
return KSFT_PASS;
}
Annotation
- Immediate include surface: `error.h`, `net/if.h`, `netinet/in.h`, `sched.h`, `stdio.h`, `sys/ioctl.h`, `sys/socket.h`, `unistd.h`.
- Detected declarations: `function localhost`, `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.