[PATCH] spinlock: indicate that a lockup is only suspected

From: Christian Borntraeger
Date: Tue May 29 2012 - 05:19:35 EST


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@xxxxxxxxxx>
---
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

--
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/