From: Sasha Levin <sasha.levin@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sched: spinlock recursion in migrate_swap_stop
Date: Mon, 19 May 2014 22:05:31 -0400 [thread overview]
Message-ID: <537AB86B.4020901@oracle.com> (raw)
In-Reply-To: <5371122D.6020605@oracle.com>
ping? It seems to be easy enough to reproduce on -next, I'd be happy to try
debug patches/fixes.
Thanks,
Sasha
On 05/12/2014 02:25 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following spew:
>
> [ 1738.758667] BUG: spinlock recursion on CPU#23, migration/23/328
> [ 1738.761291] lock: 0xffff8801f93b0c30, .magic: dead4ead, .owner: migration/23/328, .owner_cpu: 23
> [ 1738.762733] CPU: 23 PID: 328 Comm: migration/23 Not tainted 3.15.0-rc5-next-20140512-sasha-00019-ga20bc00-dirty #456
> [ 1738.764081] ffff8801f93b0c30 ffff8805505efbc8 ffffffff9453e1ec 0000000000000004
> [ 1738.764914] ffff8805505cb000 ffff8805505efbe8 ffffffff94531095 ffff8801f93b0c30
> [ 1738.765120] ffffffff9583485e ffff8805505efc08 ffffffff945310c0 ffff8801f93b0c30
> [ 1738.765120] Call Trace:
> [ 1738.768386] dump_stack (lib/dump_stack.c:52)
> [ 1738.768386] spin_dump (kernel/locking/spinlock_debug.c:68 (discriminator 6))
> [ 1738.768386] spin_bug (kernel/locking/spinlock_debug.c:76)
> [ 1738.768386] do_raw_spin_lock (kernel/locking/spinlock_debug.c:84 kernel/locking/spinlock_debug.c:135)
> [ 1738.768386] _raw_spin_lock_nested (kernel/locking/spinlock.c:362 (discriminator 2))
> [ 1738.768386] ? migrate_swap_stop (arch/x86/include/asm/paravirt.h:804 kernel/sched/sched.h:1406 kernel/sched/core.c:1099)
> [ 1738.768386] ? _raw_spin_lock (kernel/locking/spinlock.c:152)
> [ 1738.768386] ? migrate_swap_stop (kernel/sched/sched.h:1393 kernel/sched/core.c:1097)
> [ 1738.768386] migrate_swap_stop (arch/x86/include/asm/paravirt.h:804 kernel/sched/sched.h:1406 kernel/sched/core.c:1099)
> [ 1738.768386] ? queue_stop_cpus_work (include/linux/cpumask.h:108 include/linux/cpumask.h:174 kernel/stop_machine.c:375)
> [ 1738.768386] multi_cpu_stop (kernel/stop_machine.c:225)
> [ 1738.768386] ? queue_stop_cpus_work (kernel/stop_machine.c:171)
> [ 1738.768386] cpu_stopper_thread (kernel/stop_machine.c:498)
> [ 1738.768386] ? put_lock_stats.isra.12 (arch/x86/include/asm/preempt.h:98 kernel/locking/lockdep.c:254)
> [ 1738.768386] ? _raw_spin_unlock_irqrestore (arch/x86/include/asm/paravirt.h:809 include/linux/spinlock_api_smp.h:160 kernel/locking/spinlock.c:191)
> [ 1738.768386] ? __this_cpu_preempt_check (lib/smp_processor_id.c:63)
> [ 1738.768386] ? trace_hardirqs_on_caller (kernel/locking/lockdep.c:2557 kernel/locking/lockdep.c:2599)
> [ 1738.768386] smpboot_thread_fn (kernel/smpboot.c:160)
> [ 1738.768386] ? __smpboot_create_thread (kernel/smpboot.c:105)
> [ 1738.768386] kthread (kernel/kthread.c:210)
> [ 1738.768386] ? complete (kernel/sched/completion.c:35)
> [ 1738.768386] ? kthread_create_on_node (kernel/kthread.c:176)
> [ 1738.768386] ret_from_fork (arch/x86/kernel/entry_64.S:553)
> [ 1738.768386] ? kthread_create_on_node (kernel/kthread.c:176)
>
>
> Thanks,
> Sasha
>
next prev parent reply other threads:[~2014-05-20 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:25 sched: spinlock recursion in migrate_swap_stop Sasha Levin
2014-05-20 2:05 ` Sasha Levin [this message]
2014-05-20 11:04 ` Peter Zijlstra
2014-05-20 13:03 ` Sasha Levin
2014-05-21 13:08 ` Sasha Levin
2014-05-21 13:19 ` Peter Zijlstra
2014-05-21 16:49 ` Peter Zijlstra
2014-05-22 2:34 ` Sasha Levin
2014-05-22 6:59 ` Peter Zijlstra
2014-05-23 4:03 ` Sasha Levin
2014-05-22 5:35 ` Srikar Dronamraju
2014-05-22 7:00 ` Peter Zijlstra
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=537AB86B.4020901@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.