linux-kernel - Re: 4.14.9 doesn't boot (regression)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFzeyHYXJKHFGqOt-R5fhMEuq8RTQLF=4=J=bwffo6mkgw@mail.gmail.com>
Date:   Fri, 29 Dec 2017 13:39:01 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Toralf Förster <toralf.foerster@....de>,
        Alexander Tsoy <alexander@...y.me>
Cc:     Andy Lutomirski <luto@...capital.net>,
        stable <stable@...r.kernel.org>,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: 4.14.9 doesn't boot (regression)

On Fri, Dec 29, 2017 at 1:17 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Yeah, other reporters of this have used gcc-6.4.0 too.
>
> But there's been some muddying of the waters there too - changing
> compilers have fixed it for some cases, but there's at least one
> report that a kernel build with gcc-7.2.0 still had the issue (and
> another that said it didn't).

Side note: I'm not convinced that we will reliably catch a compiler
version change in our dependency analysis, so it's probably best to
"make clean" between switching compilers to make sure that you don't
have old object files with the old compiler.

> But the MCORE2 was consistent for several people - including you.
> Until this point.

.. and our build infrastructure definitely _should_ catch compiler
switch changes automatically and force a re-build.

                  Linus