From: Johannes Weiner <hannes@saeurebad.de>
To: Avi Kivity <avi@qumranet.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
LKML <linux-kernel@vger.kernel.org>,
andrea@qumranet.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: Circular vma locking with kvm, seems to be mmu notifiers related
Date: Wed, 13 Aug 2008 10:49:10 +0200 [thread overview]
Message-ID: <87od3x9u61.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <48A29D0D.9010801@qumranet.com> (Avi Kivity's message of "Wed, 13 Aug 2008 11:36:29 +0300")
Hi Avi,
Avi Kivity <avi@qumranet.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 .
Hannes
next prev parent reply other threads:[~2008-08-13 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 0:17 Circular vma locking with kvm, seems to be mmu notifiers related Max Krasnyansky
2008-08-13 8:36 ` Avi Kivity
2008-08-13 8:49 ` Johannes Weiner [this message]
2008-08-13 9:01 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87od3x9u61.fsf@skyscraper.fehenstaub.lan \
--to=hannes@saeurebad.de \
--cc=andrea@qumranet.com \
--cc=avi@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.