From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id BB7BA3857415; Mon,  2 May 2022 21:51:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB7BA3857415
From: "adhemerval.zanella at linaro dot org"
 <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29115] vfork()-based posix_spawn() has more failure modes
 than fork()-based one
Date: Mon, 02 May 2022 21:51:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: adhemerval.zanella at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29115-131-wVh7XEBsP9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29115-131@http.sourceware.org/bugzilla/>
References: <bug-29115-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2022 21:51:01 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29115

--- Comment #12 from Adhemerval Zanella <adhemerval.zanella at linaro dot o=
rg> ---
(In reply to Carlos O'Donell from comment #10)
> All of this makes me suspect that blocking vfork is the wrong semantic. It
> needs to be enabled in the kernel otherwise the CRIU use case is *not met=
*.
>=20

We need the CLONE_VFORK semantic as a QoI. Otherwise, it would require
synchronizing with a pipe or similar facility and thus require additional
resources (with might fail under some constraint environments).

> We can't add CLONE_NEWTIME and yet require all of userspace to move away
> from vfork/clone which is the fastest and least-memory intensive way to
> clone a process.
>=20
> This change adds significant code to the implementation. Please involve t=
he
> CRIU developers and see if this can't be solved in the kernel first. I
> haven't seen any justification that there are blockers to this in the ker=
nel.

I tend to agree it adds maintainability, but I think since we have some ker=
nel
with timestamp support not having a fallback or if kernel developers decide=
 to
not fix it, it will make posix_spawn an unappealing API.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=