From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: arch/x86/include/asm/trace/irq_vectors.h:50 suspicious rcu_dereference_check() usage!
Date: Wed, 3 Jul 2013 01:28:01 -0400 [thread overview]
Message-ID: <20130703052801.GA2591@redhat.com> (raw)
[ 3206.433900] ===============================
[ 3206.434449] [ INFO: suspicious RCU usage. ]
[ 3206.434999] 3.10.0+ #40 Not tainted
[ 3206.435468] -------------------------------
[ 3206.436018] /home/davej/src/linux-dj/arch/x86/include/asm/trace/irq_vectors.h:50 suspicious rcu_dereference_check() usage!
[ 3206.437383]
other info that might help us debug this:
[ 3206.438388]
RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 0
[ 3206.439733] RCU used illegally from extended quiescent state!
[ 3206.440474] no locks held by trinity-child1/31470.
[ 3206.441096]
stack backtrace:
[ 3206.441667] CPU: 3 PID: 31470 Comm: trinity-child1 Not tainted 3.10.0+ #40
[ 3206.445412] 0000000000000000 ffff880244e03f60 ffffffff816ec1a2 ffff880244e03f90
[ 3206.447288] ffffffff810b8b07 ffff88022e069890 ffff880207809f58 0000000000000006
[ 3206.449335] 0000003e127b97d8 ffff880244e03fa8 ffffffff8102629e 0000000000000282
[ 3206.451405] Call Trace:
[ 3206.452676] <IRQ> [<ffffffff816ec1a2>] dump_stack+0x19/0x1b
[ 3206.454390] [<ffffffff810b8b07>] lockdep_rcu_suspicious+0xe7/0x120
[ 3206.456086] [<ffffffff8102629e>] smp_trace_reschedule_interrupt+0x17e/0x290
[ 3206.457876] [<ffffffff8170022f>] trace_reschedule_interrupt+0x6f/0x80
[ 3206.459593] <EOI> [<ffffffff8114a847>] ? user_enter+0x87/0xd0
[ 3206.461279] [<ffffffff816fa6c5>] do_page_fault+0x45/0x50
[ 3206.462872] [<ffffffff816f6fe2>] page_fault+0x22/0x30
next reply other threads:[~2013-07-03 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 5:28 Dave Jones [this message]
2013-07-03 11:46 ` arch/x86/include/asm/trace/irq_vectors.h:50 suspicious rcu_dereference_check() usage! Steven Rostedt
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=20130703052801.GA2591@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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