From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 568B014B06C; Thu, 18 Sep 2025 17:56:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758218171; cv=none; b=dA53Rrty9dNcgiKUeRAojChBdx34kAPsT3wz+HzggCc84wSBGn9CnG34ulrFVoJJKd7lDB5DtBDrYZU7qo8rdqYspIEoeHEAq171eAT2Al/HEGGQNrdov92w2LCPDdifPUUado/jg2FoLC6cA6eB70yZVPjU3svh/6TRnwkIkY0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758218171; c=relaxed/simple; bh=mEfVkBpEmX4LqDSdnh5MGlyopQoeHAPLnvqvAtXytRA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=FJb6cXPcpkaMuzjhp8dUbdWlGoyq2J9FcqOhGMFvyJyRDn/XmVpmieMEhvFi313SzpKGRF7z2JE4wr3IpTjnrGueFzV7iMmlZBIdU7lOOwzW5Wq1y6ldQorrH9Chxc6Z2jiTY1AT7kGNvcPnPqp2ujYqrn/UnXaJtAHSoWtTFkw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=soMw9Xnj; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="soMw9Xnj" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7BD01C4CEE7; Thu, 18 Sep 2025 17:56:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1758218171; bh=mEfVkBpEmX4LqDSdnh5MGlyopQoeHAPLnvqvAtXytRA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=soMw9Xnj+exAZ2k8HgMA91ndd6uOHczKxaGV9dhZx9DL3fmpsG3RkkqOQKF8Dgo0m ou2AY8VcM8wE7AqAa5ioL45ieaVEOapn85yGQRf+EiIUv8hTFsXNgwcTCwu1y2O6Zp IeMOKHjRkHg0LNc6PhPP7lu+n2iiX3HCw4E/uvFrO74qag4qYtUb3G9ZdqmKsC9DX4 3pxZ2+ipeB+WyBXaOvrqoMK92Cbn8IxcWyBBXesgf32AP9SuvuzKarbTlkp8EOGcTl UyDbvx6rrmuLhWCkAHvQeQXluiGnULUCyDrjnZzJ6+jwbD98sg2pstQGE4de9eOpqb 9jHtxj2T2gtEw== Date: Thu, 18 Sep 2025 18:56:02 +0100 From: Mark Brown To: Will Deacon Cc: brauner@kernel.org, "Rick P. Edgecombe" , Deepak Gupta , Szabolcs Nagy , "H.J. Lu" , Florian Weimer , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Valentin Schneider , Shuah Khan , linux-kernel@vger.kernel.org, Catalin Marinas , jannh@google.com, Andrew Morton , Yury Khrustalev , Wilco Dijkstra , linux-kselftest@vger.kernel.org, linux-api@vger.kernel.org, Kees Cook , Adhemerval Zanella Netto Subject: Re: [PATCH v21 4/8] fork: Add shadow stack support to clone3() Message-ID: <21954e72-94e9-433a-a155-222c9052d4c6@sirena.org.uk> References: <20250916-clone3-shadow-stack-v21-0-910493527013@kernel.org> <20250916-clone3-shadow-stack-v21-4-910493527013@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XiyciUMuZFVOfLZH" Content-Disposition: inline In-Reply-To: X-Cookie: Victory uber allies! --XiyciUMuZFVOfLZH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 18, 2025 at 05:04:06PM +0100, Will Deacon wrote: > On Thu, Sep 18, 2025 at 01:38:53PM +0100, Will Deacon wrote: > > It would be great if Christian could give this the thumbs up, given that > > it changes clone3(). I think the architecture parts are all ready at this > > point. > ah, I may have spoken too soon :/ Well, there's also the fact that this is based on the vfs tree (or would have conflicts with it). > Catalin pointed me at this glibc thread: > https://marc.info/?l=glibc-alpha&m=175811917427562 > which sounds like they're not entirely on board with the new ABI. I think we're getting there on that one, and the main thing they're asking for is the ability to reuse the GCS after the thread has exited which would be orthogonal to this stuff. I see Catalin replied on the glibc side so I'll direct most of my reply there. It would be really helpful to get a clear idea of where we're going with this series, it's been almost landed for an incredibly long time and having it in that state is getting disruptive to doing cleanup to try to factor code out of the arches especially with the RISC-V stuff also up in the air. I do think the issues glibc have with this are orthogonal to the changes here so hopefully this can go as is. --XiyciUMuZFVOfLZH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmjMR7EACgkQJNaLcl1U h9D1nQf/S4za9m0EXxhhOOufFtQwWatoF5T4w9ZO30g2u5/wuQAFZeTtARtrFj4I Xm26dM7BBBElSdWXIWVxzROT10yXZTN0Hl50o6jhgohNXiV+Bf0dpAR+rGHp7sDh 0/TpMZMKikrTMhN89mQoHzvIktHJW1v14t3eUTrE/GZaPMdoIg1hIGY00tEVSArg nraXjUQMb4uSswTMGJWAzMIiQWQfJ7A+7Yj7Zu14xD+cY55s+xVeAQ2HmRufGpkB k7LBGaC7bzkqn7QkqMbwF558gcSC3Nl0WEvzndmxg4i9aN+Xafl4+kQVogguI39S UfARm8uNUebl5zS2zY71r5esgHQCXA== =Qji3 -----END PGP SIGNATURE----- --XiyciUMuZFVOfLZH--