perf: warning in perf_event_delayed_put

From: Sasha Levin
Date: Thu Apr 03 2014 - 10:20:04 EST


Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest
-next kernel I've stumbled on the following warning, which I happen
to hit quite often:

[ 357.437823] WARNING: CPU: 19 PID: 28 at kernel/events/core.c:7554 perf_event_delayed_put+0x64/0x80()
[child196:9542] Chose rand_syscalls.[ 357.441036] Modules linked in:
[ 357.442041] CPU: 19 PID: 28 Comm: rcuop/16 Not tainted 3.14.0-next-20140402-sasha-00013-g0cfaf7e-dirty #367
[ 357.445082] 0000000000000009 ffff88003e37fcd8 ffffffff944beb13 0000000000000003
[ 357.447245] 0000000000000000 ffff88003e37fd18
ffffffff9115a37c 0000000000000000
[ 357.449747] ffff880464e63000 ffff880464e63000 ffff880464e64a80 ffffffff95e8d170
[ 357.453659] Call Trace:
[ 357.454401] dump_stack (lib/dump_stack.c:52)
[ 357.455735] warn_slowpath_common (kernel/panic.c:418)
[ 357.457395] warn_slowpath_null (kernel/panic.c:453)
[ 357.458618] perf_event_delayed_put (kernel/events/core.c:7554 (discriminator 3))
[ 357.461861] delayed_put_task_struct (kernel/exit.c:165 include/linux/jump_label.h:105 include/trace/events/sched.h:207 kernel/exit.c:166)
[ 357.463530] ? kill_orphaned_pgrp (kernel/exit.c:162)
[ 357.465035] ? kill_orphaned_pgrp (kernel/exit.c:162)
[ 357.466981] rcu_nocb_kthread (include/linux/rcupdate.h:324 kernel/rcu/rcu.h:115 kernel/rcu/tree_plugin.h:2338)
[ 357.469129] ? rcu_nocb_kthread (kernel/rcu/rcu.h:84 kernel/rcu/tree_plugin.h:2336)
[ 357.471961] ? preempt_count_sub (kernel/sched/core.c:2527)
[ 357.473873] ? bit_waitqueue (kernel/sched/wait.c:291)
[ 357.475647] ? rcu_cpu_notify (kernel/rcu/tree_plugin.h:2276)
[ 357.477478] kthread (kernel/kthread.c:219)
[ 357.479168] ? kthread_create_on_node (kernel/kthread.c:185)
[ 357.482077] ret_from_fork (arch/x86/kernel/entry_64.S:555)
[ 357.483628] ? kthread_create_on_node (kernel/kthread.c:185)


Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/