linux-kernel - Re: Circular vma locking with kvm, seems to be mmu notifiers related

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:	Wed, 13 Aug 2008 12:01:03 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Johannes Weiner <hannes@...urebad.de>
CC:	Max Krasnyansky <maxk@...lcomm.com>,
	LKML <linux-kernel@...r.kernel.org>, andrea@...ranet.com,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: Circular vma locking with kvm, seems to be mmu notifiers related

Johannes Weiner wrote:
> Hi Avi,
>
> Avi Kivity <avi@...ranet.com> writes:
>
>   
>> Max Krasnyansky wrote:
>>     
>>> Got this on the latest mainline git.
>>> There are already a couple of lockdep/kvm threads. So maybe it's known.
>>>
>>> =============================================
>>> [ INFO: possible recursive locking detected ]
>>> 2.6.27-rc2 #36
>>> ---------------------------------------------
>>> qemu-system-x86/3445 is trying to acquire lock:
>>>  (&anon_vma->lock){--..}, at: [<ffffffff8029f84d>] mm_take_all_locks+0x8d/0xf0
>>>
>>> but task is already holding lock:
>>>  (&anon_vma->lock){--..}, at: [<ffffffff8029f84d>] mm_take_all_locks+0x8d/0xf0
>>>
>>>   
>>>       
>> Seems to be a false positive.  mmu_take_all_locks takes (surprise!)
>> all anon_vma->locks belonging to an mm, and takes special care not to
>> deadlock while doing this.
>>
>> We need to communicate this to lockdep somehow.
>>     
>
> I think Peter already annotated this in
> 454ed842d55740160334efc9ad56cfef54ed37bc .
>
>   

Excellent, thanks for the info.

-- 
error compiling committee.c: too many arguments to function

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