From: Marco Elver <elver@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: syzbot <syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
sean.j.christopherson@intel.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>,
vkuznets@redhat.com, wanpengli@tencent.com,
"the arch/x86 maintainers" <x86@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: linux-next build error (9)
Date: Mon, 22 Jun 2020 15:12:39 +0200 [thread overview]
Message-ID: <CANpmjNNb7P6eemu2=Pt7WKjfuh7VAcy5eDODUkJgkQFjzGRdGw@mail.gmail.com> (raw)
In-Reply-To: <CANpmjNMJL2euWekeJ-pRcW7-BQaDCmfCSr=8Z3Mfnz-ugtUX4g@mail.gmail.com>
On Mon, 22 Jun 2020 at 13:06, Marco Elver <elver@google.com> wrote:
>
> On Mon, 22 Jun 2020 at 11:49, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Mon, Jun 22, 2020 at 02:37:12AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: 27f11fea Add linux-next specific files for 20200622
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=138dc743100000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=41c659db5cada6f4
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=dbf8cf3717c8ef4a90a0
> > > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+dbf8cf3717c8ef4a90a0@syzkaller.appspotmail.com
> > >
> > > ./arch/x86/include/asm/kvm_para.h:99:29: error: inlining failed in call to always_inline 'kvm_handle_async_pf': function attribute mismatch
> > > ./arch/x86/include/asm/processor.h:824:29: error: inlining failed in call to always_inline 'prefetchw': function attribute mismatch
> > > ./arch/x86/include/asm/current.h:13:44: error: inlining failed in call to always_inline 'get_current': function attribute mismatch
> > > arch/x86/mm/fault.c:1353:1: error: inlining failed in call to always_inline 'handle_page_fault': function attribute mismatch
> > > ./arch/x86/include/asm/processor.h:576:29: error: inlining failed in call to always_inline 'native_swapgs': function attribute mismatch
> > > ./arch/x86/include/asm/fsgsbase.h:33:38: error: inlining failed in call to always_inline 'rdgsbase': function attribute mismatch
> > > ./arch/x86/include/asm/irq_stack.h:40:29: error: inlining failed in call to always_inline 'run_on_irqstack_cond': function attribute mismatch
> > > ./include/linux/debug_locks.h:15:28: error: inlining failed in call to always_inline '__debug_locks_off': function attribute mismatch
> > > ./include/asm-generic/atomic-instrumented.h:70:1: error: inlining failed in call to always_inline 'atomic_add_return': function attribute mismatch
> > > kernel/locking/lockdep.c:396:29: error: inlining failed in call to always_inline 'lockdep_recursion_finish': function attribute mismatch
> > > kernel/locking/lockdep.c:4725:5: error: inlining failed in call to always_inline '__lock_is_held': function attribute mismatch
> >
> > Hurmph, I though that was cured in GCC >= 8. Marco?
>
> Yeah, time to upgrade syzbot's compiler. This experimental gcc 9.0.0
> still has the bug, but stable gcc 9 doesn't. For now, I think this
> requires no fixes on the kernel side.
#syz invalid
compiler upgraded.
next prev parent reply other threads:[~2020-06-22 13:12 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 [this message]
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
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='CANpmjNNb7P6eemu2=Pt7WKjfuh7VAcy5eDODUkJgkQFjzGRdGw@mail.gmail.com' \
--to=elver@google.com \
--cc=bp@alien8.de \
--cc=dvyukov@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=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).