From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) by sourceware.org (Postfix) with ESMTPS id 188B3385842F for ; Mon, 11 Jul 2022 16:56:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 188B3385842F Received: by mail-oi1-x231.google.com with SMTP id r82so7379245oig.2 for ; Mon, 11 Jul 2022 09:56:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6naVEKg5hIw/7JtG5KV5Jh126VpH1UA/obi6Ev606q8=; b=Q0anl6uuJb8JPnT+2mLI/qRQjqeME5R2dq4QBrSOiAaq3AcM4eVzE+9GdD4OecAa2M +LZke8Zis4msoZgFSZBf//u+DMB5QHzYkx+kli2mQzKSVcOH4V/c27SiZG+MpkamVLZZ ifjcoqwJKxhUJFsD1nlj/AyTETKV0QcGUg06/UIg1s9oWhlilOd8UwSBYyNojum5cku8 QItyCfe+w93nYL60sMZl6oXdwbYDjuEthKXoQhBi96bABOa5Q8mEN5cNsaTP86NYJFSh z7lxyf2OoRnkVDWYtnUGROYGVHxMyLb+Pcn10FL+Qno4H7n2qcTqL89JmXgPpILIup34 Os2g== X-Gm-Message-State: AJIora/oW7feStdYIof+zUZr/d7Fb3HzuBtely4aGtTuo7x2WqOPc40o bXGxr7fk/yLSqh7KBPmLvsgpgwqpXAqh5A== X-Google-Smtp-Source: AGRyM1sTfexD53KyPjL4HP/fL8eHfNF/ZFwU0oXkUtdp1xT9zWOqMCVptqwmC9qzKuzOelaBnEykhw== X-Received: by 2002:a05:6808:2019:b0:339:f990:ec7d with SMTP id q25-20020a056808201900b00339f990ec7dmr4111672oiw.232.1657558603253; Mon, 11 Jul 2022 09:56:43 -0700 (PDT) Received: from smtpclient.apple ([2804:431:c7cb:5bec:a591:bf2:d8b8:7a84]) by smtp.gmail.com with ESMTPSA id m43-20020a056870562b00b001048f70e03dsm3407621oao.15.2022.07.11.09.56.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jul 2022 09:56:43 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: [PATCH v5 0/2] Linux: Fix posix_spawn when user with time namespaces From: Adhemerval Zanella In-Reply-To: <55438381-3aee-01d4-bde0-7b61e2857057@redhat.com> Date: Mon, 11 Jul 2022 13:56:39 -0300 Cc: libc-alpha@sourceware.org Content-Transfer-Encoding: 7bit Message-Id: <5F91F11D-5357-41B8-9943-7013FEE1D899@linaro.org> References: <20220530174918.3056804-1-adhemerval.zanella@linaro.org> <55438381-3aee-01d4-bde0-7b61e2857057@redhat.com> To: Carlos O'Donell X-Mailer: Apple Mail (2.3696.100.31) X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 16:56:45 -0000 > On 11 Jul 2022, at 12:32, Carlos O'Donell 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.