[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2fc62e3-934c-5c24-da99-8efa706051d7@cn.fujitsu.com>
Date: Mon, 30 Oct 2017 16:43:33 +0800
From: Dou Liyang <douly.fnst@...fujitsu.com>
To: Fengguang Wu <fengguang.wu@...el.com>,
Juergen Gross <jgross@...e.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Waiman Long <longman@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, <akataria@...are.com>,
<boris.ostrovsky@...cle.com>, <chrisw@...s-sol.org>,
<hpa@...or.com>, <jeremy@...p.org>, <rusty@...tcorp.com.au>,
<virtualization@...ts.linux-foundation.org>,
<xen-devel@...ts.xenproject.org>
Subject: Re: [locking/paravirt] static_key_disable_cpuslocked(): static key
'virt_spin_lock_key+0x0/0x20' used before call to jump_label_init()
Hi Fengguang,
There are two different warning.
At 10/30/2017 03:35 PM, Fengguang Wu wrote:
> On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote:
>> Hi Linus,
>>
>> Up to now we see the below boot error/warnings when testing v4.14-rc6.
>>
The original warning:
WARNING:at_arch/x86/events/intel/core.c:#intel_pmu_handle_irq: 1
in v4.14-rc6, which happens rarely.
>> They hit the RC release mainly due to various imperfections in 0day's
>> auto bisection. So I manually list them here and CC the likely easy to
>> debug ones to the corresponding maintainers in the followup emails.
>>
>> boot_successes: 4700
>> boot_failures: 247
>
> [...]
>
>> WARNING:at_kernel/jump_label.c:#static_key_disable_cpuslocked: 7
>
This is a new warning in tip tree, and the patch has sent[1].
[1]https://lkml.org/lkml/2017/10/28/4
we may need do it in v4.14-rc6, not in tip tree directly.
Thanks,
dou.
Powered by blists - more mailing lists