Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <452f3642-04fd-aa32-920e-5ad5925c0c91@redhat.com>
Date:   Mon, 13 Dec 2021 16:06:49 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.0
Subject: Re: [PATCH 0/2] KVM: x86: Fix dangling page reference in TDP MMU
Content-Language: en-US
To:     Ignat Korchagin <ignat@cloudflare.com>,
        linux-kernel <linux-kernel@vger.kernel.org>, kvm@vger.kernel.org
Cc:     Sean Christopherson <seanjc@google.com>, bgardon@google.com,
        dmatlack@google.com, stevensd@chromium.org,
        kernel-team <kernel-team@cloudflare.com>
References: <20211213112514.78552-1-pbonzini@redhat.com>
 <CALrw=nEM6LEAD8LA1Bd15=8BK=TFwwwAMKy_DWRrDkD=r+1Tqg@mail.gmail.com>
From:   Paolo Bonzini <pbonzini@redhat.com>
In-Reply-To: <CALrw=nEM6LEAD8LA1Bd15=8BK=TFwwwAMKy_DWRrDkD=r+1Tqg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12/13/21 14:43, Ignat Korchagin wrote:
> The only difference I noticed is the presence of __tdp_mmu_set_spte
> between zap_gfn_range and __handle_changed_spte, which is absent from
> the original stacktrace.

That's just a difference in inlining decisions, so it doesn't really matter.

Let's see if Sean has some more ideas or finds something obviously wrong 
in my patch.

Paolo