[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f360715b-e61b-7e68-1aa9-84df51331d95@redhat.com>
Date: Tue, 5 Jan 2021 19:06:23 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Ben Gardon <bgardon@...gle.com>, leohou1402 <leohou1402@...il.com>
Cc: "maciej.szmigiero@...cle.com" <maciej.szmigiero@...cle.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"cannonmatthews@...gle.com" <cannonmatthews@...gle.com>,
"peterx@...hat.com" <peterx@...hat.com>,
"pshier@...gle.com" <pshier@...gle.com>,
"pfeiner@...gle.com" <pfeiner@...gle.com>,
"junaids@...gle.com" <junaids@...gle.com>,
"jmattson@...gle.com" <jmattson@...gle.com>,
"yulei.kernel@...il.com" <yulei.kernel@...il.com>,
"kernellwp@...il.com" <kernellwp@...il.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Subject: Re: reproducible BUG() in kvm_mmu_get_root() in TDP MMU
On 05/01/21 18:49, Ben Gardon wrote:
> for_each_tdp_mmu_root(kvm, root) {
> kvm_mmu_get_root(kvm, root);
> <Do something, yield the MMU lock>
> kvm_mmu_put_root(kvm, root);
> }
>
> In these cases the get and put root calls are there to ensure that the
> root is not freed while the function is running, however they do this
> too well. If the put root call reduces the root's root_count to 0, it
> should be removed from the roots list and freed before the MMU lock is
> released. However the above pattern never bothers to free the root.
> The following would fix this bug:
>
> -kvm_mmu_put_root(kvm, root);
> +if (kvm_mmu_put_root(kvm, root))
> + kvm_tdp_mmu_free_root(kvm, root);
Is it worth writing a more complex iterator struct, so that
for_each_tdp_mmu_root takes care of the get and put?
Paolo
Powered by blists - more mailing lists