linux-kernel - [BUG 2.6.38] unlocked spinlock detected in hrtimer code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20110428083525.GB2431@osiris.boeblingen.de.ibm.com>
Date:	Thu, 28 Apr 2011 10:35:25 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-kernel@...r.kernel.org
Subject: [BUG 2.6.38] unlocked spinlock detected in hrtimer code

Hi Thomas,

while performing excessive cpu hotplug tests within a guest where the host was
completly overloaded (opening all possible race windows) I got this one:

Apr 27 14:11:33 h0529m4 kernel: BUG: spinlock already unlocked on CPU#0, kworker/4:2/43553
Apr 27 14:11:33 h0529m4 kernel: lock: 0000000088325f00, .magic: dead4ead, .owner: <none>/-1, .owner_cpu: -1
Apr 27 14:11:33 h0529m4 kernel: CPU: 0 Not tainted 2.6.38 #16
Apr 27 14:11:33 h0529m4 kernel: Process kworker/4:2 (pid: 43553, task: 000000007ca18838, ksp: 00000000669dfc48)
Apr 27 14:11:33 h0529m4 kernel: 0000000000000000 00000000669dfca0 0000000000000002 0000000000000000 
Apr 27 14:11:33 h0529m4 kernel:       00000000669dfd40 00000000669dfcb8 00000000669dfcb8 00000000005275c6 
Apr 27 14:11:33 h0529m4 kernel:       0000000000000000 0000000000000000 0000000000000000 000000000000000b 
Apr 27 14:11:33 h0529m4 kernel:       000000000000000c 00000000669dfd00 0000000000000000 0000000000000000 
Apr 27 14:11:33 h0529m4 kernel:       0000000000565740 00000000001008f0 00000000669dfca0 00000000669dfce8 
Apr 27 14:11:33 h0529m4 kernel: Call Trace:
Apr 27 14:11:33 h0529m4 kernel: ([<00000000001007f6>] show_trace+0xee/0x144)
Apr 27 14:11:33 h0529m4 kernel: [<0000000000348632>] do_raw_spin_unlock+0xbe/0xc4
Apr 27 14:11:33 h0529m4 kernel: [<0000000000530c2c>] _raw_spin_unlock_irqrestore+0x40/0xa4
Apr 27 14:11:33 h0529m4 kernel: [<00000000001722aa>] hrtimer_try_to_cancel+0x62/0xe0
Apr 27 14:11:33 h0529m4 kernel: [<0000000000172352>] hrtimer_cancel+0x2a/0x58
Apr 27 14:11:33 h0529m4 kernel: [<000000000014f50a>] do_exit+0x5ca/0x7d4
Apr 27 14:11:33 h0529m4 kernel: [<000000000016d3c4>] kthread+0x9c/0xac
Apr 27 14:11:33 h0529m4 kernel: [<000000000053166a>] kernel_thread_starter+0x6/0xc
Apr 27 14:11:33 h0529m4 kernel: [<0000000000531664>] kernel_thread_starter+0x0/0xc
Apr 27 14:11:33 h0529m4 kernel: INFO: lockdep is turned off.

I didn't look any further into it and it doesn't look like it is reproducible.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/