From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: posix_spawn and vfork
Date: Sat, 04 May 2019 15:59:00 -0000 [thread overview]
Message-ID: <d5fe7d8b-be9a-4f88-34ac-5b25ce926110@cs.ucla.edu> (raw)
In-Reply-To: <87woj6oaer.fsf@oldenburg2.str.redhat.com>
Florian Weimer wrote:
> doing this is worthwhile because
> it increases test coverage for our vfork implementation. I think we
> need to provide a working vfork.
Yes; regardless of whether we use vfork to implement posix_spawn, too many
programs rely on vfork to withdraw it any time in the foreseeable future.
next prev parent reply other threads:[~2019-05-04 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:18 Florian Weimer
2019-05-02 13:22 ` Adhemerval Zanella
2019-05-04 9:07 ` Florian Weimer
2019-05-04 15:59 ` Paul Eggert [this message]
2019-05-06 12:41 ` Adhemerval Zanella
2019-05-06 12:50 ` Florian Weimer
2019-05-06 19:58 ` Adhemerval Zanella
2019-05-07 8:51 ` Florian Weimer
2019-05-07 13:32 ` Adhemerval Zanella
2019-05-06 12:34 ` Adhemerval Zanella
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=d5fe7d8b-be9a-4f88-34ac-5b25ce926110@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).