elf: fail if vnode already open for writing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start with the related TODO in kernel-src/sys/elf.c at line 155 and read the surrounding ELF loading logic. Determine what should happen when the vnode is already open for writing, then implement the TODO’s failure behavior. Done when that case fails as intended and the relevant project checks pass.
Written by the indexing model from the issue text.
Description
- Dominant language
- C
- Stars
- 629
- Forks
- 36
- Avg merge
- 1d 23m
- Merged PRs (30d)
- 8
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
-
iovec: add size overflow checkPossibly taken @ian0318git claimed this 1 day ago. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Mathewnd/Astral#109 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
feat(palindrome): add C solutionPossibly taken @aadiitya2007 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
techcsispit/code-corner#58 · 1 comment ·
Maintainers usually reply within 1 day
-
logo request
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
fastfetch-cli/fastfetch#2661 ·
Maintainers usually reply within 1 day
-
Mark ignored Mac OS partitions RecoveryOSContainer and iBootSystemContainerPossibly taken @meven claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
storaged-project/udisks#1559 ·