tools/testing/selftests/proc/proc-2-is-kthread.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/proc/proc-2-is-kthread.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/proc/proc-2-is-kthread.c- Extension
.c- Size
- 1786 bytes
- Lines
- 54
- 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.herrno.hfcntl.hstring.hunistd.h
Detected Declarations
function Copyright
Annotated Snippet
#undef NDEBUG
#include <assert.h>
#include <errno.h>
#include <fcntl.h>
#include <string.h>
#include <unistd.h>
int main(void)
{
/*
* The following solutions don't really work:
*
* 1) jit kernel module which creates kernel thread:
* test becomes arch-specific,
* problems with mandatory module signing,
* problems with lockdown mode,
* doesn't work with CONFIG_MODULES=n at all,
* kthread creation API is formally unstable internal kernel API,
* need a mechanism to report test kernel thread's PID back,
*
* 2) ksoftirqd/0 and kswapd0 look like stable enough kernel threads,
* but their PIDs are unstable.
*
* Check against kthreadd which always seem to exist under pid 2.
*/
int fd = open("/proc/2/status", O_RDONLY);
assert(fd >= 0);
char buf[4096];
ssize_t rv = read(fd, buf, sizeof(buf));
assert(0 <= rv && rv < sizeof(buf));
buf[rv] = '\0';
assert(strstr(buf, "Kthread:\t1\n"));
return 0;
}
Annotation
- Immediate include surface: `assert.h`, `errno.h`, `fcntl.h`, `string.h`, `unistd.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.