From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [locking/mutex] e274795ea7 WARNING: CPU: 0 PID: 1 at arch/x86/include/asm/fpu/internal.h:348 __switch_to
Date: Sat, 18 Feb 2017 11:28:45 +0100 [thread overview]
Message-ID: <20170218102845.GF6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170218085746.fojbfjlzdahri5qw@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Sat, Feb 18, 2017 at 04:57:46PM +0800, Fengguang Wu wrote:
> Hi Peter,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit e274795ea7b7caa0fd74ef651594382a69e2a951
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Wed Jan 11 14:17:48 2017 +0100
> Commit: Ingo Molnar <mingo@kernel.org>
> CommitDate: Sat Jan 14 11:14:38 2017 +0100
That commit has been in the tree for over a month now.. And I've never
seen a warning like this before.
>
> locking/mutex: Fix mutex handoff
>
> [ 13.377261] Write protecting the kernel text: 15320k
> [ 13.378910] Write protecting the kernel read-only data: 6316k
> [ 13.380655] NX-protecting the kernel data: 9256k
> [ 13.382475] x86/mm: Checked W+X mappings: passed, no W+X pages found.
> [ 13.384781] ------------[ cut here ]------------
> [ 13.386327] WARNING: CPU: 0 PID: 1 at arch/x86/include/asm/fpu/internal.h:348 __switch_to+0x1b6/0x260
What tree is this? on current next/master that file doesn't have a WARN
on that line.
next prev parent reply other threads:[~2017-02-18 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 8:57 [locking/mutex] e274795ea7 WARNING: CPU: 0 PID: 1 at arch/x86/include/asm/fpu/internal.h:348 __switch_to Fengguang Wu
2017-02-18 10:28 ` Peter Zijlstra [this message]
2017-02-18 13:53 ` Fengguang Wu
2017-02-18 14:26 ` Peter Zijlstra
2017-02-19 2:53 ` Fengguang Wu
2017-02-20 10:25 ` [tip:locking/core] fork: Fix task_struct alignment tip-bot for Peter Zijlstra
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=20170218102845.GF6500@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.