spinlock: Indicate that a lockup is only suspected
authorChristian Borntraeger <borntraeger@de.ibm.com>
Tue, 29 May 2012 09:18:44 +0000 (11:18 +0200)
committerIngo Molnar <mingo@kernel.org>
Wed, 6 Jun 2012 09:34:20 +0000 (11:34 +0200)
commit8a173b1476d126674104c7c5c6cef0bcd824b001
tree788d4c8a018ee939f7b7fcbb782a23259e274d2c
parentc7f5f4ab10ce4e05b9f8877f1fd112faba71f175
spinlock: Indicate that a lockup is only suspected

On an over-committed KVM system we got a:

  "BUG: spinlock lockup on CPU#2, swapper/2/0"

message 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>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1338283124-7063-1-git-send-email-borntraeger@de.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
lib/spinlock_debug.c