mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] spinlock: indicate that a lockup is only suspected
@ 2012-05-29  9:18 Christian Borntraeger
  2012-06-06 15:14 ` [tip:core/urgent] spinlock: Indicate " tip-bot for Christian Borntraeger
  0 siblings, 1 reply; 2+ messages in thread
From: Christian Borntraeger @ 2012-05-29  9:18 UTC (permalink / raw)
  To: linux-kernel
  Cc: akpm, mingo, Rusty Russell, Michael S. Tsirkin, Christian Borntraeger

On an over-committed KVM system we got a
"BUG: spinlock lockup on CPU#2, swapper/2/0" on the heavily contended
virtio blk spinlock.
While we might want to reconsider the locking of virtio-blk (lock is
held while switching to the host) this patch tries to make the message
clearer: the lockup is only suspected

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 lib/spinlock_debug.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/spinlock_debug.c b/lib/spinlock_debug.c
index 525d160..1d2be56 100644
--- a/lib/spinlock_debug.c
+++ b/lib/spinlock_debug.c
@@ -118,7 +118,7 @@ static void __spin_lock_debug(raw_spinlock_t *lock)
 		/* lockup suspected: */
 		if (print_once) {
 			print_once = 0;
-			spin_dump(lock, "lockup");
+			spin_dump(lock, "lockup suspected");
 #ifdef CONFIG_SMP
 			trigger_all_cpu_backtrace();
 #endif
-- 
1.7.10.3


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-06-06 15:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-29  9:18 [PATCH] spinlock: indicate that a lockup is only suspected Christian Borntraeger
2012-06-06 15:14 ` [tip:core/urgent] spinlock: Indicate " tip-bot for Christian Borntraeger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®