linux-kernel - Re: linux-next build error (9)

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: <20200624090029.5fa2dc1f@canb.auug.org.au>
Date:   Wed, 24 Jun 2020 09:00:29 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Marco Elver <elver@...gle.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        syzbot <syzbot+dbf8cf3717c8ef4a90a0@...kaller.appspotmail.com>,
        bp@...en8.de, hpa@...or.com, jmattson@...gle.com, joro@...tes.org,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-next@...r.kernel.org, mingo@...hat.com, pbonzini@...hat.com,
        sean.j.christopherson@...el.com, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de, vkuznets@...hat.com, wanpengli@...cent.com,
        x86@...nel.org
Subject: Re: linux-next build error (9)

Hi Marco,

On Tue, 23 Jun 2020 13:24:48 +0200 Marco Elver <elver@...gle.com> wrote:
>
> On Tue, Jun 23, 2020 at 08:17PM +1000, Stephen Rothwell wrote:
> > Hi Peter,
> > 
> > On Tue, 23 Jun 2020 11:32:30 +0200 Peter Zijlstra <peterz@...radead.org> wrote:  
> > >
> > > I suppose the next quest is finding a s390 compiler version that works
> > > and then bumping the version test in the aforementioned commit.  
> > 
> > Not a lot of help, but my Debian cross compiler seems to work:
> > 
> > $ s390x-linux-gnu-gcc --version
> > s390x-linux-gnu-gcc (Debian 9.3.0-13) 9.3.0  
> 
> Rummaging through changelogs led me to 8.3.0 as the first good GCC. Also
> confirmed by building that version and compiling a file that breaks with
> older versions. It seems the first major version to fix it was 9, but
> backported to 8.3. This is for all architectures.
> 
> Suggested patch below.
> 
> Thanks,
> -- Marco
> 
> ------ >8 ------  
> 
> From: Marco Elver <elver@...gle.com>
> Date: Tue, 23 Jun 2020 12:57:42 +0200
> Subject: [PATCH] kasan: Fix required compiler version
> 
> The first working GCC version to satisfy
> CC_HAS_WORKING_NOSANITIZE_ADDRESS is GCC 8.3.0.
> 
> Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89124
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Signed-off-by: Marco Elver <elver@...gle.com>
> ---
>  lib/Kconfig.kasan | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
> index 7a496b885f46..19fba15e99c6 100644
> --- a/lib/Kconfig.kasan
> +++ b/lib/Kconfig.kasan
> @@ -16,7 +16,7 @@ config CC_HAS_KASAN_SW_TAGS
>  	def_bool $(cc-option, -fsanitize=kernel-hwaddress)
>  
>  config CC_HAS_WORKING_NOSANITIZE_ADDRESS
> -	def_bool !CC_IS_GCC || GCC_VERSION >= 80000
> +	def_bool !CC_IS_GCC || GCC_VERSION >= 80300
>  
>  config KASAN
>  	bool "KASAN: runtime memory debugger"
> -- 
> 2.27.0.111.gc72c7da667-goog
> 

Thanks for tracking that down.  I will add that patch to the tip tree
merge for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped