LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Daniel Micay" <danielmicay@gmail.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	pali.rohar@gmail.com, sre@kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, "Kevin Hilman" <khilman@kernel.org>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	ivo.g.dimitrov.75@gmail.com,
	"Patrik Bachan" <patrikbachan@gmail.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	"Mickuláš Qwertz" <abcloriens@gmail.com>,
	"Clayton Craft" <clayton@craftyguy.net>,
	"Martijn Braam" <martijn@brixit.nl>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Filip Matijević" <filip.matijevic.pz@gmail.com>,
	"Jinbum Park" <jinb.park7@gmail.com>,
	"Russell King" <rmk+kernel@armlinux.org.uk>
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
Date: Fri, 20 Apr 2018 08:05:17 -0700	[thread overview]
Message-ID: <CAGXu5j+6D3PiVc9SR4+31ZGDC2r5uWJOw8Sn3cDhXdNqBGH+hQ@mail.gmail.com> (raw)
In-Reply-To: <20180420073402.GA9356@amd>

On Fri, Apr 20, 2018 at 12:34 AM, Pavel Machek <pavel@ucw.cz> wrote:
> On Sun 2018-04-15 11:00:06, Kees Cook wrote:
>> On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek <pavel@ucw.cz> 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=arm make lib/string.o
>> >>
>> >> And the winner is:
>> >>
>> >> ee333554fed55555a986a90bb097ac7f9d6f05bf is the first bad commit
>> >> commit ee333554fed55555a986a90bb097ac7f9d6f05bf
>> >> Author: Jinbum Park <jinb.park7@gmail.com>
>> >> Date:   Tue Mar 6 01:39:24 2018 +0100
>> > ...
>> >
>> >>     Acked-by: Kees Cook <keescook@chromium.org>
>> >>     Signed-off-by: Jinbum Park <jinb.park7@gmail.com>
>> >>     Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>> >
>> > 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.
>>
>> 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.
>
> Daniel, Kees: any news?
>
> I'm aware you did not specify which Monday :-).

Hi! Sorry, I got distracted. So the .config you sent me builds fine
with my cross compiler. I suspect this is something specific to ELDK's
compiler. I can try some other compiler versions. What version of gcc
is failing?

-Kees

-- 
Kees Cook
Pixel Security

  reply	other threads:[~2018-04-20 15:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  6:55 Stephen Rothwell
2018-04-04  7:48 ` ARM compile failure in " Pavel Machek
2018-04-04 17:58   ` Tony Lindgren
2018-04-04 18:15     ` Pavel Machek
2018-04-04 18:46     ` Pavel Machek
2018-04-04 19:59       ` Tony Lindgren
2018-04-04 20:18         ` FORTIFY_SOURCE breaks ARM compilation in -next -- was " Pavel Machek
2018-04-15 17:39           ` [regression v4.17-rc0] " Pavel Machek
2018-04-15 18:00             ` Kees Cook
2018-04-15 20:58               ` Pavel Machek
2018-04-20  7:34               ` Pavel Machek
2018-04-20 15:05                 ` Kees Cook [this message]
2018-04-20 17:21                   ` Russell King - ARM Linux
2018-04-20 19:15                   ` Pavel Machek
2018-04-20 19:18                     ` Daniel Micay
2018-04-20 19:28                       ` Pavel Machek
2018-04-20 19:30                         ` Daniel Micay
2018-04-20 20:30                           ` Pavel Machek
2018-04-04  7:50 ` x32 suspend failuer " Pavel Machek
2018-04-04  7:58   ` Rafael J. Wysocki
2018-04-04  8:49     ` Pavel Machek
2018-04-05 12:25       ` update-binfmts breaking suspend was " Pavel Machek
2018-04-05 20:30         ` Pavel Machek
2018-04-05 22:27           ` Rafael J. Wysocki
     [not found]           ` <SN4PR2101MB073673B12998428D48DA62E5CBBA0@SN4PR2101MB0736.namprd21.prod.outlook.com>
     [not found]             ` <20180406144355.GA20605@bombadil.infradead.org>
2018-04-11  4:30               ` update-binfmts breaking suspend Matthew Wilcox
2018-04-11  6:09                 ` Pavel Machek
2018-04-06 22:41   ` x32 suspend failuer in Re: linux-next: Tree for Apr 4 Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGXu5j+6D3PiVc9SR4+31ZGDC2r5uWJOw8Sn3cDhXdNqBGH+hQ@mail.gmail.com \
    --to=keescook@chromium.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=abcloriens@gmail.com \
    --cc=arnd@arndb.de \
    --cc=clayton@craftyguy.net \
    --cc=danielmicay@gmail.com \
    --cc=filip.matijevic.pz@gmail.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=jinb.park7@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=martijn@brixit.nl \
    --cc=pali.rohar@gmail.com \
    --cc=patrikbachan@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=regressions@leemhuis.info \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=sakari.ailus@linux.intel.com \
    --cc=serge@hallyn.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    --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' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).