From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/1] kvm: fix circular locking dependency
Date: Sun, 08 Feb 2009 11:43:46 +0200 [thread overview]
Message-ID: <498EA952.5040508@redhat.com> (raw)
In-Reply-To: <20090208052805.GA4437@amt.cnet>
Marcelo Tosatti wrote:
> On Fri, Feb 06, 2009 at 08:57:31AM +0000, Mark McLoughlin wrote:
>
>> On Thu, 2009-02-05 at 10:52 -0800, Chris Wright wrote:
>>
>>> * Mark McLoughlin (markmc@redhat.com) wrote:
>>>
>>>> kvm->slots_lock is outer to kvm->lock, so take slots_lock
>>>> in kvm_vm_ioctl_assign_device() before taking kvm->lock,
>>>> rather than taking it in kvm_iommu_map_memslots().
>>>>
Applied, but,
>>> stable? maint/2.6.29?
>>>
>> Yep, my bad - Avi, please add:
>>
>> Cc: stable@kernel.org
>>
>> and pull into maint/2.6.29
>>
>
> ACK.
>
>
At this point in maint/2.6.29's lifetime, it gets updated by pulling
from Linus, and stable is only updated after Linus is updated.
(It's the same rule, really -- only commit to a maintenance branch after
upstream has been fixed, to ensure we don't have a maint fix without a
corresponding upstream fix)
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-02-08 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 10:25 2.6.29-rc3 circular locking dependency detected Mark McLoughlin
2009-02-03 10:47 ` Avi Kivity
2009-02-03 16:35 ` Mark McLoughlin
2009-02-05 18:23 ` [PATCH 1/1] kvm: fix circular locking dependency Mark McLoughlin
2009-02-05 18:52 ` Chris Wright
2009-02-06 8:57 ` Mark McLoughlin
2009-02-08 5:28 ` Marcelo Tosatti
2009-02-08 9:43 ` Avi Kivity [this message]
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=498EA952.5040508@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox