KeSetTimer doesn't fire when there is a heavy DPC load
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105
- Forks
- 34
- Avg merge
- 3d 39m
- Merged PRs (30d)
- 5
Description
Emulated DPC threads running at thread priority time critical which starves the thread pool timer threads resulting in the timers not firing.
This breaks the eBPF for Windows epoch cleanup code which requires a timer to initiate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the emulated KeSetTimer path alongside the emulated DPC threads and thread pool timer threads. Reproduce the behavior under heavy DPC load, then verify that timers fire and the eBPF for Windows epoch cleanup code can initiate its timer-driven cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100