Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp5483827pxb; Wed, 26 Jan 2022 13:07:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJzUdRKysKq6tRYUtjF6ZID95u5084DMyP0hOTVLnPrShPKn0ig4IHnAh4JhkbE2hbFRe/mZ X-Received: by 2002:a05:6a00:198a:: with SMTP id d10mr722264pfl.2.1643231240980; Wed, 26 Jan 2022 13:07:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643231240; cv=none; d=google.com; s=arc-20160816; b=LGV8ZjuAmVoprgMtliGa4J+m7nUD1H7QEQaK3q5Eyh40xglJgMPWOryNDi6NMY+d1K BJ4NyHjfY/XUym3QoY59TGg3CRgLiXsgvuUpF1N9cwDXp0DaG+00i7JycKUq/xxqmzle /Ht1Pea9cYW3OCjSkdEyH4NziFb4SX5gIpzbaAGAs6nr5QbXLOg0aL4rimloXPp4HBo6 MS8CrmuqiQ761e28cveHNnWefqopV9pfxSyGmoi6UZQOQOv6kzf25RDjQY4BLLmmByiU ebw61vB2G/TS/kpMcXyHM8rmFaE5Qlk+Lp7uRZ4EF0WHneZyXlqoTO6MWqJAxq2tW8nG A97w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:in-reply-to:date :references:subject:cc:to:from; bh=a31Ct9ptxsOf60Ec4J19+QUmPTv38RE/Xfzd4V8Ahp0=; b=uYaVQGFz/1jACbNFvNhFvXw9N2GLpX7Jhu40VuDSlzCbjF2wNUqVI6o+ifkDbVgQCa H1IWgVFb+/iVrAV1tEPXyyRIjeVnhGoxX7DJ+EeoBOi/b7f1Kc7bEdUiXQ4Y+BOjmd3l U7EZXt2Cz0A7d8NHud2D0KH7ABRjk34r3HxJIopZHJy3yt6PaiXUTaR1Ncrq/IMImr8E iBfxyr57IGbr/ahJhWevLVIhmpoTCDS+rEzms5opyCbgqdOuXnYt3mctXXxswrfWd98j pBGDIjwNzpcytxmGOcOCNS/t3wRp/L3VhUcCVqtKSmuACKbImlXpCK3K1qulu9XDHkPC LCZA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c22si284342pls.503.2022.01.26.13.07.05; Wed, 26 Jan 2022 13:07:20 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240516AbiAZLLl (ORCPT + 99 others); Wed, 26 Jan 2022 06:11:41 -0500 Received: from albireo.enyo.de ([37.24.231.21]:62006 "EHLO albireo.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233490AbiAZLLk (ORCPT ); Wed, 26 Jan 2022 06:11:40 -0500 Received: from [172.17.203.2] (port=37899 helo=deneb.enyo.de) by albireo.enyo.de ([172.17.140.2]) with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) id 1nCgCt-0012zO-1Z; Wed, 26 Jan 2022 11:11:19 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.94.2) (envelope-from ) id 1nCg2p-00078D-Rn; Wed, 26 Jan 2022 12:00:55 +0100 From: Florian Weimer To: Christian Brauner Cc: Mathieu Desnoyers , Thomas Gleixner , linux-kernel , Peter Zijlstra , paulmck , Boqun Feng , "H. Peter Anvin" , Paul Turner , linux-api , shuah , linux-kselftest , Andy Lutomirski , Dave Watson , Andrew Morton , Russell King , Andi Kleen , Christian Brauner , Ben Maurer , rostedt , Josh Triplett , Linus Torvalds , Catalin Marinas , Will Deacon , Michael Kerrisk , Joel Fernandes Subject: Re: [RFC PATCH 02/15] rseq: Remove broken uapi field layout on 32-bit little endian References: <20220124171253.22072-1-mathieu.desnoyers@efficios.com> <20220124171253.22072-3-mathieu.desnoyers@efficios.com> <20220125122156.v2f5anzcs35i3rii@wittgenstein> <1234069751.70438.1643121673355.JavaMail.zimbra@efficios.com> <1445357149.71067.1643137248305.JavaMail.zimbra@efficios.com> <20220126080327.4g4pkv3haenxt2m6@wittgenstein> Date: Wed, 26 Jan 2022 12:00:55 +0100 In-Reply-To: <20220126080327.4g4pkv3haenxt2m6@wittgenstein> (Christian Brauner's message of "Wed, 26 Jan 2022 09:03:27 +0100") Message-ID: <87fspa92xk.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Christian Brauner: > On Tue, Jan 25, 2022 at 02:00:48PM -0500, Mathieu Desnoyers wrote: >> So users of the uapi rseq.h (as an API) can still use >> rseq_abi->rseq_cs before and after the change. >> >> Based on this, I am inclined to remove the union, and just make the >> rseq_cs field a __u64. >> >> Any objections ? > > I do like it fwiw. But since I haven't been heavily involved in the > userspace usage of this I can't speak confidently to the regression > potential of a change like this. But I would think that we should risk > it instead of dragging a pointless union around forever. I don't think glibc needs changes for this, it will keep building just fine. We'll need to adjust the included kernel header fragment that could be used by applications in some corner cases, but that's it.