From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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, elver@google.com
Subject: Re: linux-next build error (9)
Date: Tue, 23 Jun 2020 11:32:30 +0200 [thread overview]
Message-ID: <20200623093230.GD4781@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200623124413.08b2bd65@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Tue, Jun 23, 2020 at 12:44:13PM +1000, Stephen Rothwell wrote:
> Hi Peter,
>
> On Mon, 22 Jun 2020 11:49:23 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> > Hurmph, I though that was cured in GCC >= 8. Marco?
>
> So what causes this? Because we got a couple of these in our s390 builds last night as well.
This is KASAN's __no_sanitize_address function attribute. Some GCC
versions are utterly wrecked when that function attribute is combined
with inlining. It wants to have matching attributes for the function
being inlined and function it is inlined into -- hence the function
attribute mismatch.
> kernel/locking/lockdep.c:805:1: error: inlining failed in call to always_inline 'look_up_lock_class': function attribute mismatch
> include/linux/debug_locks.h:15:28: error: inlining failed in call to always_inline '__debug_locks_off': function attribute mismatch
>
> s390-linux-gcc (GCC) 8.1.0 / GNU ld (GNU Binutils) 2.30
*groan*... So supposedly it was supposed to work on GCC-8 and later, see
commit 7b861a53e46b6. But now it turns out there's some later versions
that fail too.
I suppose the next quest is finding a s390 compiler version that works
and then bumping the version test in the aforementioned commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-23 9:33 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 [this message]
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
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=20200623093230.GD4781@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
--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).