From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1284FC433E1 for ; Wed, 15 Jul 2020 06:33:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E0252206F4 for ; Wed, 15 Jul 2020 06:33:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728666AbgGOGdk (ORCPT ); Wed, 15 Jul 2020 02:33:40 -0400 Received: from albireo.enyo.de ([37.24.231.21]:44584 "EHLO albireo.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725823AbgGOGdj (ORCPT ); Wed, 15 Jul 2020 02:33:39 -0400 Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jvayt-0000Pz-3w; Wed, 15 Jul 2020 06:33:27 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1jvawb-00039g-W6; Wed, 15 Jul 2020 08:31:05 +0200 From: Florian Weimer To: Chris Kennelly Cc: Peter Oskolkov , Mathieu Desnoyers , Peter Oskolkov , Peter Zijlstra , linux-kernel , Thomas Gleixner , paulmck , Boqun Feng , "H. Peter Anvin" , Paul Turner , linux-api , Christian Brauner , carlos Subject: Re: [RFC PATCH 2/4] rseq: Allow extending struct rseq References: <20200714030348.6214-1-mathieu.desnoyers@efficios.com> <20200714030348.6214-3-mathieu.desnoyers@efficios.com> <775688146.12145.1594748580461.JavaMail.zimbra@efficios.com> Date: Wed, 15 Jul 2020 08:31:05 +0200 In-Reply-To: (Chris Kennelly's message of "Tue, 14 Jul 2020 22:34:38 -0400") Message-ID: <87k0z5xpau.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Chris Kennelly: > When glibc provides registration, is the anticipated use case that a > library would unregister and reregister each thread to "upgrade" it to > the most modern version of interface it knows about provided by the > kernel? Absolutely not, that is likely to break other consumers because an expected rseq area becomes dormant instead. > There, I could assume an all-or-nothing registration of the new > feature--limited only by kernel availability for thread > homogeneity--but inconsistencies across early adopter libraries would > mean each thread would have to examine its own TLS to determine if a > feature were available. Exactly. Certain uses of seccomp can also have this effect, presenting a non-homogeneous view.