From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by sourceware.org (Postfix) with ESMTPS id 3BAB63860C3E for ; Mon, 14 Jun 2021 16:00:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3BAB63860C3E Received: by mail.kernel.org (Postfix) with ESMTPSA id A191661246; Mon, 14 Jun 2021 16:00:40 +0000 (UTC) Date: Mon, 14 Jun 2021 17:00:22 +0100 From: Mark Brown To: Jeremy Linton Cc: Catalin Marinas , Will Deacon , Szabolcs Nagy , Dave Martin , "H . J . Lu" , Yu-cheng Yu , linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, libc-alpha@sourceware.org Subject: Re: [PATCH v2 0/3] arm64: Enable BTI for the executable as well as the interpreter Message-ID: <20210614160022.GD5646@sirena.org.uk> References: <20210604112450.13344-1-broonie@kernel.org> <43e67d7b-aab9-db1f-f74b-a87ba7442d47@arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="48TaNjbzBVislYPb" Content-Disposition: inline In-Reply-To: <43e67d7b-aab9-db1f-f74b-a87ba7442d47@arm.com> X-Cookie: Some restrictions may apply. User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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, 14 Jun 2021 16:00:43 -0000 --48TaNjbzBVislYPb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 10, 2021 at 11:28:12AM -0500, Jeremy Linton wrote: > Of course, there is a good chance I've messed something up or i'm missing > something. I should really validate the /lib/ld-linux behavior itself too. I > guess this could just as well be a glibc issue (f34 has glibc 2.33-5 which If it were a glibc issue that'd mean that glibc would have to somehow manage to disable PROT_BTI after the kernel set it. I think I've found the issue, will send a new version out shortly - we just weren't actually parsing the properties on the main executable properly. A new version should appear shortly. --48TaNjbzBVislYPb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmDHfRUACgkQJNaLcl1U h9AViAf7BQlBEp1qfFrcbTv9BB7RBU0iHWkfYy+AKB9GoPYYLoDvlohzR126bXfA Hxj+jdxOhQKlfpj5cI1TPGkLgz4WqQZam16q1G6otbiCJoBS4wIYWhDzgR5I2PoV WAaImFLt98lGbE2fyR8Wgt4eyrcgEa53RHjUEXHKnDsDrqSiEwoYzrRTBbR/qorJ b6yCV6onhNvUHUNiEZPDNPgm2k+U/KOJOyKVNe8qEZJnDT0Oto0XGPvb00SuIgJB vnNOWvTJ9rb27rRnHXqzEkDfLEvufCmpoUMqFxpSNYPTw4yZHriArituaIZDDxvL PcARtbiD2f41ItW7KZunNPr1rz2fmA== =02Sb -----END PGP SIGNATURE----- --48TaNjbzBVislYPb--