thread: add reaper for kernel threads
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start with the linked TODO in kernel-src/sys/thread.c at line 78 and read the surrounding thread lifecycle code. Trace how kernel threads finish and where their resources need cleanup; done when a reaper handles completed kernel threads safely. The issue gives no tests or detailed completion criteria, so first identify the existing lifecycle checks and test setup.
Written by the indexing model from the issue text.
Description
- Dominant language
- C
- Stars
- 629
- Forks
- 36
- Avg merge
- 12h 26m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Mathewnd/Astral
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
iovec: add size overflow checkPossibly taken @ian0318git claimed this 6 days ago. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
priority:medium type:chore
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
crazy-goat/php-fpm-ng#1041 ·
Maintainers usually reply within 1 day
-
Bug Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Test failure on FreeBSD: #26 unexpected system_clock sourcePossibly taken A pull request linked to this issue is open or already merged. Openlow priority rt_lib tests
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day