From: Alexey Izbyshev <izbyshev@ispras.ru>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v2] linux: Add fallback for clone failure on posix_spawn (BZ#29115)
Date: Tue, 03 May 2022 19:10:31 +0300 [thread overview]
Message-ID: <e601d83c47160b7c4f5a3059e856c4ce@ispras.ru> (raw)
In-Reply-To: <87h766bt18.fsf@igel.home>
On 2022-05-03 17:16, Andreas Schwab wrote:
> On Mai 03 2022, Adhemerval Zanella via Libc-alpha wrote:
>
>> The patch fixes by retrying the clone syscall with just CLONE_VFORK
>> if clone fails with a non transient failure (ENOMEM and EAGAIN still
>> returns failure to caller).
>
> I there any point for CLONE_VFORK without CLONE_VM? Since the VM isn't
> shared, there should be no harm for both processes to run concurrently.
Not the patch author, but in case of posix_spawn() processes won't run
concurrently in a meaningful way because the parent will block on read()
from the error pipe. So it seems like a moot point.
Alexey
next prev parent reply other threads:[~2022-05-03 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 13:46 Adhemerval Zanella
2022-05-03 14:16 ` Andreas Schwab
2022-05-03 16:10 ` Alexey Izbyshev [this message]
2022-05-03 16:06 ` Alexey Izbyshev
2022-05-03 16:37 ` 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=e601d83c47160b7c4f5a3059e856c4ce@ispras.ru \
--to=izbyshev@ispras.ru \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).