linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marco Elver <elver@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	syzbot <syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com>,
	bp@alien8.de, hpa@zytor.com, jmattson@google.com,
	joro@8bytes.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	mingo@redhat.com, pbonzini@redhat.com,
	sean.j.christopherson@intel.com, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
	x86@kernel.org
Subject: Re: linux-next build error (9)
Date: Wed, 24 Jun 2020 09:00:29 +1000	[thread overview]
Message-ID: <20200624090029.5fa2dc1f@canb.auug.org.au> (raw)
In-Reply-To: <20200623112448.GA208112@elver.google.com>

[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]

Hi Marco,

On Tue, 23 Jun 2020 13:24:48 +0200 Marco Elver <elver@google.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@infradead.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@google.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@canb.auug.org.au>
> Signed-off-by: Marco Elver <elver@google.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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-06-23 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  9:37 linux-next build error (9) syzbot
2020-06-22  9:49 ` Peter Zijlstra
2020-06-22 11:06   ` Marco Elver
2020-06-22 13:12     ` Marco Elver
2020-06-23  2:44   ` Stephen Rothwell
2020-06-23  9:32     ` Peter Zijlstra
2020-06-23 10:09       ` Marco Elver
2020-06-23 10:17       ` Stephen Rothwell
2020-06-23 11:24         ` Marco Elver
2020-06-23 23:00           ` Stephen Rothwell [this message]

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=20200624090029.5fa2dc1f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bp@alien8.de \
    --cc=elver@google.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).