tools/testing/selftests/proc/thread-self.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/proc/thread-self.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/proc/thread-self.c- Extension
.c- Size
- 1740 bytes
- Lines
- 65
- 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.hsched.hstdio.hunistd.hsys/mman.hsys/wait.hproc.h
Detected Declarations
function ffunction main
Annotated Snippet
// Test that /proc/thread-self gives correct TGID/PID.
#undef NDEBUG
#include <assert.h>
#include <sched.h>
#include <stdio.h>
#include <unistd.h>
#include <sys/mman.h>
#include <sys/wait.h>
#include "proc.h"
int f(void *arg)
{
char buf1[64], buf2[64];
pid_t pid, tid;
ssize_t rv;
pid = sys_getpid();
tid = sys_gettid();
snprintf(buf1, sizeof(buf1), "%u/task/%u", pid, tid);
rv = readlink("/proc/thread-self", buf2, sizeof(buf2));
assert(rv == strlen(buf1));
buf2[rv] = '\0';
assert(streq(buf1, buf2));
if (arg)
exit(0);
return 0;
}
int main(void)
{
const int PAGE_SIZE = sysconf(_SC_PAGESIZE);
pid_t pid;
void *stack;
/* main thread */
f((void *)0);
stack = mmap(NULL, 2 * PAGE_SIZE, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0);
assert(stack != MAP_FAILED);
/* side thread */
pid = clone(f, stack + PAGE_SIZE, CLONE_THREAD|CLONE_SIGHAND|CLONE_VM, (void *)1);
assert(pid > 0);
pause();
return 0;
}
Annotation
- Immediate include surface: `assert.h`, `sched.h`, `stdio.h`, `unistd.h`, `sys/mman.h`, `sys/wait.h`, `proc.h`.
- Detected declarations: `function f`, `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.