From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214705] New: execve(2) omits EACCES due to capabilities
Date: Wed, 13 Oct 2021 02:36:41 +0000 [thread overview]
Message-ID: <bug-214705-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214705
Bug ID: 214705
Summary: execve(2) omits EACCES due to capabilities
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: dspeyer@gmail.com
Regression: No
The man page for execve lists only 4 reasons the syscall can fail with
errno==EACCES. In fact, there is at least one more. If the binary being
executed has a setfattr'ed capability such as CAP_IPC_LOCK which is not
supported in the caller's kernel namespace (docker container), execve will fail
with this error.
I just spent a great deal of frustrating effort searching for a non-existent
elf interpreter or mount-noexec issue because I trusted this man page.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-10-13 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 2:36 bugzilla-daemon [this message]
2021-10-15 22:10 ` [Bug 214705] execve(2) omits EACCES due to capabilities bugzilla-daemon
2021-10-16 18:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-214705-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox