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

[Avi Kivity]

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.

--
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/