linux-kernel - Re: inconsistent lock state. (kvm)

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 27 Sep 2008 12:56:06 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Dave Jones <davej@...hat.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: inconsistent lock state. (kvm)

Dave Jones wrote:
> I just triggered this with just modprobe kvm_intel ; rmmod kvm kvm_intel
>
> 	Dave
>
> =================================
> [ INFO: inconsistent lock state ]
> 2.6.26.3-29.fc9.x86_64.debug #1
> ---------------------------------
> inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
> Xorg/2680 [HC1[1]:SC0[0]:HE0:SE1] takes:
>  (kvm_lock){+-..}, at: [<ffffffffa0463ad6>] decache_vcpus_on_cpu+0x20/0xbd [kvm]
>   

This is sort of known, which is why decache_vcpus_on_cpu no longer exists.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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