From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RCU hangs in latest linux-next
Date: Fri, 22 Jun 2012 09:33:20 -0700 [thread overview]
Message-ID: <20120622163320.GB2470@linux.vnet.ibm.com> (raw)
In-Reply-To: <1340379615.11290.1.camel@lappy>
On Fri, Jun 22, 2012 at 05:40:15PM +0200, Sasha Levin wrote:
> Hi Paul,
>
> The following tends to happen quite often when I run the trinity fuzzer on a KVM tools guest using latest linux-next:
Hello, Sasha,
I had a wait_event() where I needed a wait_event_interruptible().
Should be fixed in the next linux-next, see:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
Thanx, Paul
> [ 242.223240] INFO: task rcu_bh:14 blocked for more than 120 seconds.
> [ 242.225587] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [ 242.230227] rcu_bh D 0000000000000000 6424 14 2 0x00000000
> [ 242.231297] ffff88000d5a1d50 0000000000000046 ffffffff84a6b020 0000000000000286
> [ 242.231995] ffff88000d5a0000 ffff88000d5a0010 ffff88000d5a1fd8 ffff88000d5a0000
> [ 242.232825] ffff88000d5a0010 ffff88000d5a1fd8 ffff88000d5b0000 ffff88000d59b000
> [ 242.233533] Call Trace:
> [ 242.233752] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.234866] [<ffffffff836e9355>] schedule+0x55/0x60
> [ 242.235827] [<ffffffff811ab3fb>] rcu_gp_kthread+0xfb/0xac0
> [ 242.236725] [<ffffffff836eae5b>] ? _raw_spin_unlock_irq+0x2b/0x80
> [ 242.237905] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.239206] [<ffffffff8116339d>] ? trace_hardirqs_on+0xd/0x10
> [ 242.240100] [<ffffffff836e91bd>] ? __schedule+0x84d/0x880
> [ 242.241917] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.244162] [<ffffffff8111b930>] ? wake_up_bit+0x40/0x40
> [ 242.245998] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.248226] [<ffffffff8111b102>] kthread+0xb2/0xc0
> [ 242.250102] [<ffffffff836ed234>] kernel_thread_helper+0x4/0x10
> [ 242.251887] [<ffffffff836eb4b4>] ? retint_restore_args+0x13/0x13
> [ 242.254243] [<ffffffff8111b050>] ? __init_kthread_worker+0x70/0x70
> [ 242.256304] [<ffffffff836ed230>] ? gs_change+0x13/0x13
> [ 242.258207] no locks held by rcu_bh/14.
> [ 242.259523] INFO: task rcu_sched:15 blocked for more than 120 seconds.
> [ 242.261795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [ 242.264267] rcu_sched D 0000000000000000 6552 15 2 0x00000000
> [ 242.266855] ffff88000d5a3d50 0000000000000046 ffffffff84964020 0000000000000286
> [ 242.269297] ffff88000d5a2000 ffff88000d5a2010 ffff88000d5a3fd8 ffff88000d5a2000
> [ 242.272035] ffff88000d5a2010 ffff88000d5a3fd8 ffff88000d528000 ffff88000d5b0000
> [ 242.274263] Call Trace:
> [ 242.275345] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.277550] [<ffffffff836e9355>] schedule+0x55/0x60
> [ 242.279317] [<ffffffff811ab3fb>] rcu_gp_kthread+0xfb/0xac0
> [ 242.281129] [<ffffffff836eae5b>] ? _raw_spin_unlock_irq+0x2b/0x80
> [ 242.283256] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.292260] [<ffffffff8116339d>] ? trace_hardirqs_on+0xd/0x10
> [ 242.292264] [<ffffffff836e91bd>] ? __schedule+0x84d/0x880
> [ 242.292268] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.292271] [<ffffffff8111b930>] ? wake_up_bit+0x40/0x40
> [ 242.292274] [<ffffffff811ab300>] ? synchronize_rcu_expedited+0x220/0x220
> [ 242.292277] [<ffffffff8111b102>] kthread+0xb2/0xc0
> [ 242.292280] [<ffffffff836ed234>] kernel_thread_helper+0x4/0x10
> [ 242.292283] [<ffffffff836eb4b4>] ? retint_restore_args+0x13/0x13
> [ 242.292286] [<ffffffff8111b050>] ? __init_kthread_worker+0x70/0x70
> [ 242.292289] [<ffffffff836ed230>] ? gs_change+0x13/0x13
> [ 242.292291] no locks held by rcu_sched/15.
>
prev parent reply other threads:[~2012-06-22 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 15:40 RCU hangs in latest linux-next Sasha Levin
2012-06-22 16:06 ` Ming Lei
2012-06-22 16:33 ` Paul E. McKenney [this message]
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=20120622163320.GB2470@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.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