Skip to contentSkip to conversation

Badness in __mutex_unlock_slowpath

DISCUSSION Chuck Ebbert 1 participant 1 message Jan 8, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <200601071551.20344.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>

Quoted 10 lines · On Sat, 7 Jan 2006 at 15:51:19 -0500 Andrew James Wade wrote:

I got this when "amaroK" started playing:

Badness in __mutex_unlock_slowpath at kernel/mutex.c:214

 [<c03538e8>] __mutex_unlock_slowpath+0x56/0x1a2
 [<c0302f08>] snd_pcm_oss_write+0x0/0x1e0
 [<c0302f3c>] snd_pcm_oss_write+0x34/0x1e0
 [<c0302f08>] snd_pcm_oss_write+0x0/0x1e0
 [<c0148221>] vfs_write+0x83/0x122
 [<c0148a36>] sys_write+0x3c/0x63
 [<c0102ba3>] sysenter_past_esp+0x54/0x75

The thread doing the unlock does not own the mutex.

Same exact check is made a few lines later in debug_mutex_unlock().

And debugging gets turned off after the first debug message prints, so there could be other problems that are not reported.

--
Chuck
Currently reading: _Thud!_ by Terry Pratchett