public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org,  Alexey Izbyshev <izbyshev@ispras.ru>,
	 Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v4 0/3] Linux: Fix posix_spawn when user with time namespaces
Date: Tue, 10 May 2022 21:18:46 +0200	[thread overview]
Message-ID: <877d6tb3hl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220510191155.1998575-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Tue, 10 May 2022 16:11:52 -0300")

* Adhemerval Zanella:

> The patchset 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.
>
> Adhemerval Zanella (3):
>   linux: Add CLONE_NEWTIME from Linux 5.6 to bits/sched.h
>   support: Add support_enter_time_namespace
>   linux: Add fallback for clone failure on posix_spawn (BZ #29115)

Christan, how likely is it that we'd get another time namespace variant
that would only become effective after execve (when the DSO is remapped
anyway)?

This is a lot of complexity in posix_spawn implementations for what is a
rather limited use case.

Thanks,
Florian


  parent reply	other threads:[~2022-05-10 19:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 19:11 Adhemerval Zanella
2022-05-10 19:11 ` [PATCH v4 1/3] linux: Add CLONE_NEWTIME from Linux 5.6 to bits/sched.h Adhemerval Zanella
2022-05-23 13:45   ` Adhemerval Zanella
2022-05-10 19:11 ` [PATCH v4 2/3] support: Add support_enter_time_namespace Adhemerval Zanella
2022-05-10 19:11 ` [PATCH v4 3/3] linux: Add fallback for clone failure on posix_spawn (BZ #29115) Adhemerval Zanella
2022-05-10 19:18 ` Florian Weimer [this message]
2022-05-11  9:21   ` [PATCH v4 0/3] Linux: Fix posix_spawn when user with time namespaces Christian Brauner
2022-05-11 16:01     ` Alexey Izbyshev
2022-05-25 12:24     ` Florian Weimer
2022-05-27 15:53       ` Andrei Vagin
2022-05-28  0:03         ` Andrei Vagin
2022-05-29 14:33           ` Christian Brauner
2022-05-30 12:58         ` Florian Weimer
2022-06-08  7:21           ` Andrei Vagin
2022-06-08  8:35             ` Florian Weimer

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=877d6tb3hl.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=brauner@kernel.org \
    --cc=carlos@redhat.com \
    --cc=izbyshev@ispras.ru \
    --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).