samples/workqueue/stall_detector/wq_stall.c
Source file repositories/reference/linux-study-clean/samples/workqueue/stall_detector/wq_stall.c
File Facts
- System
- Linux kernel
- Corpus path
samples/workqueue/stall_detector/wq_stall.c- Extension
.c- Size
- 3074 bytes
- Lines
- 99
- Domain
- Support Tooling And Documentation
- Bucket
- samples
- Inferred role
- Support Tooling And Documentation: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/workqueue.hlinux/wait.hlinux/atomic.hlinux/sched.h
Detected Declarations
function stall_work2_fnfunction stall_work1_fnfunction wq_stall_initfunction wq_stall_exitmodule init wq_stall_init
Annotated Snippet
module_init(wq_stall_init);
module_exit(wq_stall_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Reproduce workqueue stall caused by PF_WQ_WORKER misuse");
MODULE_AUTHOR("Breno Leitao <leitao@debian.org>");Annotation
- Immediate include surface: `linux/module.h`, `linux/workqueue.h`, `linux/wait.h`, `linux/atomic.h`, `linux/sched.h`.
- Detected declarations: `function stall_work2_fn`, `function stall_work1_fn`, `function wq_stall_init`, `function wq_stall_exit`, `module init wq_stall_init`.
- Atlas domain: Support Tooling And Documentation / samples.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.