linux-kernel - Re: kisskb: FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Tue Jan 25, 18:24

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: <CAK8P3a2uM=vVx7WwZDi_H7dZPxBtr5-EeS5ETQVoah1Cek0W2A@mail.gmail.com>
Date:   Wed, 26 Jan 2022 16:25:44 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Arnd Bergmann <arnd@...db.de>, Kees Cook <keescook@...omium.org>,
        Yury Norov <yury.norov@...il.com>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kisskb: FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Tue Jan 25, 18:24

On Wed, Jan 26, 2022 at 1:37 PM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Wed, Jan 26, 2022 at 1:26 PM Arnd Bergmann <arnd@...db.de> wrote:
> > I ran the preprocessed code through cvise[1], bisecting for a reduced
> > test case that fails on gcc-8 but succeeds on gcc-9. The reduced
> > case is still fairly complex, and it appears to only happen in the
> > presence of an inline asm. Narrowing down the compiler versions shows
> > that anything after gcc-9.2 does not warn, but 9.1 and earlier versions do,
> > which is further indication that  it was probably a false-positive that got
> > fixed in gcc.
>
> Thanks for investigating! So let's ignore this.
>
> FTR, my gcc-9 is 9.4.0, i.e. >= 9.2.

Ok, if it comes up again, I suppose we can make the warning conditional on
the compiler warning.

         Arnd