From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v5 0/2] Linux: Fix posix_spawn when user with time namespaces
Date: Mon, 11 Jul 2022 13:56:39 -0300 [thread overview]
Message-ID: <5F91F11D-5357-41B8-9943-7013FEE1D899@linaro.org> (raw)
In-Reply-To: <55438381-3aee-01d4-bde0-7b61e2857057@redhat.com>
> On 11 Jul 2022, at 12:32, Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 5/30/22 13:49, Adhemerval Zanella via Libc-alpha wrote:
>> The patchset also adds some support to tests the fallback code
>> to use only use CLONE_VFORK. It uses unshare directly because
>> it simpler than add container support.
>>
>> v5: Use a MAP_SHARED page to communicate error on prepare phase from
>> helper process.
>
> The current progress is that it seems we may get the upstream Linux kernel
> to change the semantics of the time namespace to take effect only after
> exec for vfork. If that goes forward we won't need these changes?
>
> I'm trying to determine if these changes constitute a blocker for 2.36.
My understanding is even kernel does change or add a new flag to handle
it, we still have released kernels that might hit this issue.
next prev parent reply other threads:[~2022-07-11 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 17:49 Adhemerval Zanella
2022-05-30 17:49 ` [PATCH v5 1/2] support: Add support_enter_time_namespace Adhemerval Zanella
2022-05-30 17:49 ` [PATCH v5 2/2] linux: Add fallback for clone failure on posix_spawn (BZ #29115) Adhemerval Zanella
2022-07-11 15:32 ` [PATCH v5 0/2] Linux: Fix posix_spawn when user with time namespaces Carlos O'Donell
2022-07-11 16:56 ` Adhemerval Zanella [this message]
2022-07-19 2:33 ` Carlos O'Donell
2022-07-19 12:56 ` Adhemerval Zanella Netto
2022-07-29 15:49 ` Carlos O'Donell
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=5F91F11D-5357-41B8-9943-7013FEE1D899@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@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).