Incorrect and confusing error message on EACCES
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- operating-systems
Research direction
Start by tracing how modinfo handles the failed file access shown in the report and how it formats the “not found” error. Check the handling of EACCES and compare it with the reported strace result. Done means permission failures are reported as permission denied or similar while missing files still report not found; the issue does not name source files or tests.
Written by the indexing model from the issue text.
Description
From Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104199.
When modinfo is unable to access a module due to path permissions it gets EACCES and that should be reported to the user as "permission denied" (or similar). It currently says "not found" which leads the user to believe that it was not there which is not the situation.
# modinfo /var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module/nvidia-current-peermem.ko.xz
modinfo: ERROR: Module /var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module/nvidia-current-peermem.ko.xz not found.
newfstatat(AT_FDCWD, "/var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module/nvidia-current-peermem.ko.xz", 0x7ffc581232c0, 0) = -1 EACCES (Permission denied)
This happens under SE Linux if the file has the wrong label.
- Dominant language
- C
- Stars
- 116
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from kmod-project/kmod
-
good first issue
Difficulty 3/5 1-2 days Newbie friendliness 35/100
kmod-project/kmod#484 · 1 reaction ·
Maintainers usually reply within 4 days
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
kmod-project/kmod#483 ·
Maintainers usually reply within 4 days
-
Various 34.x backport nominationsPossibly taken @lucasdemarchi claimed this 5 days ago. Openfor-lucas
kmod-project/kmod#480 · 2 comments · 1 assignee ·
Maintainers usually reply within 4 days
-
Use `malloc` function attributePossibly taken @crims0n claimed this 4 days ago. Opengood first issue
Difficulty 3/5 1-2 days Newbie friendliness 52/100
kmod-project/kmod#479 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
kmod-project/kmod#476 · 1 comment ·
Maintainers usually reply within 4 days
All issues in kmod-project/kmod
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PecanProject/sipnet#435 · 1 comment ·
Maintainers usually reply within 2 days
-
SDL_GPU Vulkan: wrong screen orientation on OpenHarmony (preTransform set without pre-rotation)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
libsdl-org/SDL#16670 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
要トリアージ 辞書
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yksr-melt/Meltype#1625 · 1 reaction ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day