From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: paulmck@linux.vnet.ibm.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
fweisbec@gmail.com
Subject: Re: rcu_read_lock() used illegally while idle!
Date: Fri, 24 May 2013 18:41:52 -0400 [thread overview]
Message-ID: <20130524224152.GC17786@redhat.com> (raw)
In-Reply-To: <1369423420.6828.226.camel@gandalf.local.home>
On Fri, May 24, 2013 at 03:23:40PM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-24 at 10:23 -0400, Dave Jones wrote:
>
> > .config: http://paste.fedoraproject.org/14281/94052971/raw/
> >
> > trace shows the problem process was 'cc1', so I was likely building a kernel
> > at the time. There was also a trinity run going on in the background.
> >
> > cmdline: nothing special..
> >
> > BOOT_IMAGE=/vmlinuz-3.10.0-rc2+ root=UUID=bee21cd9-1852-4d1d-9e9d-2e44332b8df1 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 consoleblank=0 console=ttyUSB0,115200 console=tty0 pause_on_oops=30 audit=0
> >
>
> OK, I'm able to reproduce this. Looks like the same issue happens from
> other ways from userspace into the kernel (the next way was tracing
> system calls).
>
> Forget the other patch. Here's a new patch that is more specific to
> tracing and context tracking.
>
> Can you try this one out, please.
It's looking good so far.
Dave
next prev parent reply other threads:[~2013-05-24 22:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 17:31 rcu_read_lock() used illegally while idle! Dave Jones
2013-05-21 23:58 ` WARNING: at kernel/rcutree.c:388 rcu_eqs_enter Dave Jones
2013-05-22 9:51 ` Paul E. McKenney
2013-05-23 15:51 ` Dave Jones
2013-05-26 18:17 ` Paul E. McKenney
2013-05-22 9:36 ` rcu_read_lock() used illegally while idle! Paul E. McKenney
2013-05-22 12:49 ` Steven Rostedt
2013-05-23 16:40 ` Dave Jones
2013-05-24 13:46 ` Steven Rostedt
2013-05-24 14:23 ` Dave Jones
2013-05-24 19:23 ` Steven Rostedt
2013-05-24 22:41 ` Dave Jones [this message]
2013-05-25 13:59 ` Dave Jones
2013-05-25 18:20 ` Steven Rostedt
2013-05-26 18:04 ` Jiri Olsa
2013-05-28 20:13 ` Dave Jones
2013-05-28 20:27 ` Steven Rostedt
2013-05-28 21:32 ` [BUG] with rcu nocb, don't call wake up holding rnp->lock (was: rcu_read_lock() used illegally while idle!) Steven Rostedt
2013-05-29 3:29 ` Paul E. McKenney
2013-06-19 18:39 ` [tip:sched/core] tracing/context-tracking: Add preempt_schedule_context() for tracing tip-bot for 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=20130524224152.GC17786@redhat.com \
--to=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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