From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 219947] New: Undocumented EAGAIN behavior for clone/pthread_create
Date: Fri, 28 Mar 2025 10:26:15 +0000 [thread overview]
Message-ID: <bug-219947-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219947
Bug ID: 219947
Summary: Undocumented EAGAIN behavior for clone/pthread_create
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: lennart.kramer@wibu.com
Regression: No
Currently, when a clone() is called with CLONE_FS (as is the case with
pthread_create), and concurrently in another thread, an execve() syscall is in
progress, the clone() call may return early with an EAGAIN error.
I think the corresponding location in the kernel returning EAGAIN is in
kernel/fork.c inside copy_fs.
The man pages currently only document cases of resource exhaustion (and a
SCHED_DEADLINE case which most people won't care about) under EAGAIN, in which
case aborting the process is reasonable, but in this case it can result in the
process exiting before the execve() syscall finishes.
This is nonsensical as the thread calling clone() was about to be deleted
anyway.
--
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:[~2025-03-28 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 10:26 bugzilla-daemon [this message]
2025-03-28 18:28 ` [Bug 219947] Undocumented EAGAIN behavior for clone/pthread_create bugzilla-daemon
2025-03-28 18:37 ` bugzilla-daemon
2025-03-28 19:44 ` bugzilla-daemon
2025-03-28 21:25 ` bugzilla-daemon
2025-03-31 6:57 ` 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-219947-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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