tools/testing/selftests/mm/droppable.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/mm/droppable.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/mm/droppable.c- Extension
.c- Size
- 1332 bytes
- Lines
- 61
- 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.
Dependency Surface
assert.hstdbool.hstdint.hstdio.hstdlib.hunistd.hsignal.hsys/mman.hlinux/mman.hkselftest.h
Detected Declarations
function Copyright
Annotated Snippet
if ((errno == EOPNOTSUPP) || (errno == EINVAL)) {
ksft_test_result_skip("MAP_DROPPABLE not supported\n");
exit(KSFT_SKIP);
}
ksft_test_result_fail("mmap error: %s\n", strerror(errno));
exit(KSFT_FAIL);
}
memset(alloc, 'A', alloc_size);
for (size_t i = 0; i < alloc_size; i += page_size)
assert(*(uint8_t *)(alloc + i));
child = fork();
assert(child >= 0);
if (!child) {
for (;;)
*(char *)malloc(page_size) = 'B';
}
for (bool done = false; !done;) {
for (size_t i = 0; i < alloc_size; i += page_size) {
if (!*(uint8_t *)(alloc + i)) {
done = true;
break;
}
}
}
kill(child, SIGTERM);
ksft_test_result_pass("MAP_DROPPABLE: PASS\n");
exit(KSFT_PASS);
}
Annotation
- Immediate include surface: `assert.h`, `stdbool.h`, `stdint.h`, `stdio.h`, `stdlib.h`, `unistd.h`, `signal.h`, `sys/mman.h`.
- Detected declarations: `function Copyright`.
- 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.