Messages in this thread |  | | Date | Sun, 15 Apr 2018 19:39:08 +0200 | From | Pavel Machek <> | 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 |
| |
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 [unhandled content-type:application/pgp-signature] |  |