possible deadlock in splinter_set_super_block
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
splinter_set_super_block does the idiomatic claim loop, but doesn't unget and get the page inside the loop.
Deadlock, or a special case because it's boot code? If a special case, add a comment?
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 at the splinter_set_super_block entry point and inspect its claim loop, including how page references are managed during boot. Determine whether the missing unget/get can deadlock; done means either correcting the page handling or documenting why this boot-time case is safe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100