linux-kernel - Re: 2.6.19-rc6-rt7: Kernel BUG at kernel/rtmutex.c:672

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Nov 2006 21:05:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
Cc:	"Linux-Kernel," <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc6-rt7: Kernel BUG at kernel/rtmutex.c:672

* Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU> wrote:

> Nov 28 03:26:39 localhost kernel: Kernel BUG at kernel/rtmutex.c:672

hm, this means the lock was taken twice by the same task: enabling 
CONFIG_PROVE_LOCKING ought to tell us the precise locking info and 
backtraces that causes this situation. I looked at the code and it wasnt 
obvious at first sight. (we should only be holding cache_chain_mutex 
here, and l3->list_lock should not be taken at this point.)

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