From: Andreas Schwab <schwab@suse.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Martin Buchholz <martinrb@google.com>,
Zack Weinberg <zackw@panix.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: system and popen fail in case of big application
Date: Thu, 13 Sep 2018 06:31:00 -0000 [thread overview]
Message-ID: <mvmworpaoxf.fsf@suse.de> (raw)
In-Reply-To: <01ffd458-794b-6d05-0635-f13437bec096@linaro.org> (Adhemerval Zanella's message of "Wed, 12 Sep 2018 22:27:28 -0300")
On Sep 12 2018, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> - vfork would be supported on Linux not because its a good interface,
> but rather than Linux policy is to not broke userspace in any case.
> And it would be supported only on architectures that already provide
> it, new ports do not automatically export vfork and they are not
> encouraged to do so. Currently ARC, alpha, s390, microblame, x86, sH,
> powerpc, hexagen, parisc, m68k, arm, and aarch64 do so (and aarch64
> only if compat mode is enabled, a 64-bit kernel only won't have vfork
> syscall). For remaining arches, glibc will just use a clone plus
> required flags (CLONE_VM | CLONE_VFORK | SIGCHLD).
That doesn't make sense. CLONE_VFORK *is* vfork in all matters, and
every architecture supports it. It's nothing different from the fact
that there is no open syscall any more, because openat does the same
(and more).
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-09-13 6:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 22:16 Sergey Melnikov
2018-09-09 22:44 ` Zack Weinberg
2018-09-09 22:47 ` Zack Weinberg
2018-09-09 23:27 ` Sergey Melnikov
2018-09-09 23:49 ` Zack Weinberg
2018-09-10 2:50 ` Martin Buchholz
2018-09-10 15:38 ` Joseph Myers
2018-09-10 15:42 ` Zack Weinberg
2018-09-10 15:43 ` Joseph Myers
[not found] ` <CA+kOe0_1k_PbJ-pjHznP4AmTJUgziAdT+4vCcCRSb7GGdvbv7Q@mail.gmail.com>
2018-09-10 15:59 ` Zack Weinberg
2018-09-10 16:55 ` Martin Buchholz
2018-09-11 20:16 ` Adhemerval Zanella
2018-09-12 16:30 ` Zack Weinberg
2018-09-12 19:46 ` Martin Buchholz
2018-09-13 1:27 ` Adhemerval Zanella
2018-09-13 6:31 ` Andreas Schwab [this message]
2018-09-13 12:30 ` Adhemerval Zanella
2018-09-18 1:18 ` Martin Buchholz
2018-09-18 1:59 ` Adhemerval Zanella
2018-09-18 2:18 ` Martin Buchholz
2018-09-18 4:31 ` Rich Felker
2018-09-12 23:08 ` Adhemerval Zanella
2018-09-13 12:11 ` Szabolcs Nagy
2018-09-14 18:42 ` Zack Weinberg
2018-09-17 10:32 ` Szabolcs Nagy
2018-09-17 18:27 ` 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=mvmworpaoxf.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=martinrb@google.com \
--cc=zackw@panix.com \
/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).