From: Pavel Machek <pavel@ucw•cz>
To: Tony Lindgren <tony@atomide•com>,
Thorsten Leemhuis <regressions@leemhuis•info>,
Linus Torvalds <torvalds@linux-foundation•org>,
arnd@arndb•de
Cc: "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, khilman@kernel•org,
aaro.koskinen@iki•fi, ivo.g.dimitrov.75@gmail•com,
patrikbachan@gmail•com, serge@hallyn•com, abcloriens@gmail•com,
clayton@craftyguy•net, martijn@brixit•nl,
sakari.ailus@linux•intel.com,
"Filip Matijević" <filip.matijevic.pz@gmail•com>,
jinb.park7@gmail•com, keescook@chromium•org,
rmk+kernel@armlinux•org.uk
Subject: [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: Sun, 15 Apr 2018 19:39:08 +0200 [thread overview]
Message-ID: <20180415173908.GA2024@amd> (raw)
In-Reply-To: <20180404201837.GA9710@amd>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
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.
And BTW, Russell, there's another regression I bisected to your
commit, that one is like two releases old, and "only" causes
compilation warnings during build with non-US locale. I even proposed
fix for that. Guess what? Ignored too.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-04-15 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:55 linux-next: Tree for Apr 4 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 ` Pavel Machek [this message]
2018-04-15 18:00 ` [regression v4.17-rc0] " Kees Cook
2018-04-15 20:58 ` Pavel Machek
2018-04-20 7:34 ` Pavel Machek
2018-04-20 15:05 ` Kees Cook
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=20180415173908.GA2024@amd \
--to=pavel@ucw$(echo .)cz \
--cc=aaro.koskinen@iki$(echo .)fi \
--cc=abcloriens@gmail$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=clayton@craftyguy$(echo .)net \
--cc=filip.matijevic.pz@gmail$(echo .)com \
--cc=ivo.g.dimitrov.75@gmail$(echo .)com \
--cc=jinb.park7@gmail$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=khilman@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=martijn@brixit$(echo .)nl \
--cc=pali.rohar@gmail$(echo .)com \
--cc=patrikbachan@gmail$(echo .)com \
--cc=regressions@leemhuis$(echo .)info \
--cc=rmk+kernel@armlinux$(echo .)org.uk \
--cc=sakari.ailus@linux$(echo .)intel.com \
--cc=serge@hallyn$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sre@kernel$(echo .)org \
--cc=tony@atomide$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox