From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: ak@linux.intel.com, x86@kernel.org
Subject: suspicious RCU usage in msr tracing.
Date: Thu, 21 Jan 2016 19:34:27 -0500 [thread overview]
Message-ID: <20160122003427.GA29240@codemonkey.org.uk> (raw)
Just hit this on Linus' current tree.
[ INFO: suspicious RCU usage. ]
4.4.0-think+ #1 Tainted: G W
-------------------------------
./arch/x86/include/asm/msr-trace.h:47 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 0
RCU used illegally from extended quiescent state!
no locks held by swapper/3/0.
stack backtrace:
CPU: 3 PID: 0 Comm: swapper/3 Tainted: G W 4.4.0-think+ #1
ffffffff8ef82ac0 c4dd1c3486ada576 ffff880468e07f08 ffffffff8e566ae1
ffff880464905340 ffff880468e07f38 ffffffff8e135bf8 ffffffff8f665b00
ffff880464918000 0000000000000000 ffff880464920000 ffff880468e07f70
Call Trace:
<IRQ> [<ffffffff8e566ae1>] dump_stack+0x4e/0x7d
[<ffffffff8e135bf8>] lockdep_rcu_suspicious+0xf8/0x110
[<ffffffff8e5b3f36>] do_trace_write_msr+0x136/0x140
[<ffffffff8e061753>] native_apic_msr_eoi_write+0x23/0x30
[<ffffffff8e054456>] smp_call_function_single_interrupt+0x36/0x50
[<ffffffff8e05447e>] smp_call_function_interrupt+0xe/0x10
[<ffffffff8ed1bdc0>] call_function_interrupt+0x90/0xa0
<EOI> [<ffffffff8e2f1b20>] ? __asan_store4+0x80/0x80
[<ffffffff8eac6477>] ? poll_idle+0x67/0xc0
[<ffffffff8eac5a94>] cpuidle_enter_state+0x174/0x430
[<ffffffff8eac5da7>] cpuidle_enter+0x17/0x20
[<ffffffff8e128ff5>] cpu_startup_entry+0x4c5/0x5a0
[<ffffffff8e128b30>] ? default_idle_call+0x60/0x60
[<ffffffff8e18d354>] ? clockevents_config_and_register+0x64/0x70
[<ffffffff8e055489>] start_secondary+0x269/0x300
[<ffffffff8e055220>] ? set_cpu_sibling_map+0x970/0x970
------------[ cut here ]------------
44 DEFINE_EVENT(msr_trace_class, write_msr,
45 TP_PROTO(unsigned msr, u64 val, int failed),
46 TP_ARGS(msr, val, failed)
47 );
Andi, could this be caused by 7f47d8cc039f8746e0038fe05f1ddcb15a2e27f0 ?
Dave
next reply other threads:[~2016-01-22 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 0:34 Dave Jones [this message]
2016-01-22 22:33 ` Andi Kleen
2016-01-22 23:51 ` Paul E. McKenney
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=20160122003427.GA29240@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome