rcore-os / rcore-os/rCore-Tutorial-v3

ch8之后主线程的kstack被错误过早回收

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
2.1k
Forks
560
PR merge metrics
No merged PRs in 30d

Description

详情参见这里

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked pull request for the details of the premature kstack reclamation after chapter 8. Trace the main thread's kstack lifetime in the relevant Rust kernel code and confirm the expected ownership and cleanup point. Done means the main thread's kstack remains available for all required execution and is reclaimed only at the correct time.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.