From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752934AbeDOU6L (ORCPT ); Sun, 15 Apr 2018 16:58:11 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:52911 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752604AbeDOU6J (ORCPT ); Sun, 15 Apr 2018 16:58:09 -0400 Date: Sun, 15 Apr 2018 22:58:07 +0200 From: Pavel Machek To: Kees Cook Cc: Daniel Micay , Tony Lindgren , Thorsten Leemhuis , Linus Torvalds , Arnd Bergmann , Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List , pali.rohar@gmail.com, sre@kernel.org, linux-arm-kernel , linux-omap@vger.kernel.org, Kevin Hilman , Aaro Koskinen , ivo.g.dimitrov.75@gmail.com, Patrik Bachan , "Serge E. Hallyn" , =?utf-8?B?TWlja3Vsw6HFoQ==?= Qwertz , Clayton Craft , Martijn Braam , Sakari Ailus , Filip =?utf-8?Q?Matijevi=C4=87?= , Jinbum Park , Russell King Subject: Re: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4 Message-ID: <20180415205807.GA4182@amd> References: <20180404165559.4cd0c12c@canb.auug.org.au> <20180404074856.GA9342@amd> <20180404175852.GI5700@atomide.com> <20180404184622.GA8608@amd> <20180404195951.GJ5700@atomide.com> <20180404201837.GA9710@amd> <20180415173908.GA2024@amd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun 2018-04-15 11:00:06, Kees Cook wrote: > On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote: > > Hi! > > > >> Thanks. > >> > >> Ok, let me try to bisect it. Compile-problem should be easy... > >> > >> Hmm. And as it is compile-problem in single file, it should even be > >> reasonably fast. I did not realize how easy it would be: > >> > >> #!/bin/bash > >> set -e > >> cp config.ok .config > >> yes '' | ARCH=3Darm make lib/string.o > >> > >> And the winner is: > >> > >> ee333554fed55555a986a90bb097ac7f9d6f05bf is the first bad commit > >> commit ee333554fed55555a986a90bb097ac7f9d6f05bf > >> Author: Jinbum Park > >> Date: Tue Mar 6 01:39:24 2018 +0100 > > ... > > > >> Acked-by: Kees Cook > >> Signed-off-by: Jinbum Park > >> Signed-off-by: Russell King > > > > So I bisect a problem in -next, and patch is merged to Linus, > > _anyway_, breaking compilation there? Neither Jinbum nor Russell even > > bother to comment. >=20 > Hi! Sorry I lost this email in my inbox. It seems this is specific to > a particular subset of arm architectures? (My local builds of arm all > succeed, for example. Can you send your failing config?) I'll take a > closer look on Monday if Daniel doesn't beat me to it. I believe it depends on gcc version really. I should get some sleep now, but details should be in the corresponding thread on lkml. I'll send you my .config privately. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --l76fUT7nc3MelDdI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlrTvN8ACgkQMOfwapXb+vLhTgCcDvOONplDwZ2uDNCkiG3G/Bdl r+IAnRjHLy9V9BdOAYE8Gwk4ejKlbl0k =MBNZ -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI--