Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Will Deacon <will@kernel.org>
To:     Peter Zijlstra <peterz@infradead.org>, aneesh.kumar@linux.ibm.com,
        Catalin Marinas <catalin.marinas@arm.com>,
        Marc Zyngier <maz@kernel.org>, steven.price@arm.com,
        Zhenyu Ye <yezhenyu2@huawei.com>
Cc:     kernel-team@android.com, Will Deacon <will@kernel.org>,
        liushixin2@huawei.com, Xiexiangyou <xiexiangyou@huawei.com>,
        linux-arm-kernel@lists.infradead.org,
        huyaqin <huyaqin1@huawei.com>, linux-mm@kvack.org,
        linux-arch@vger.kernel.org, zhurui3@huawei.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: tlb: fix the TTL value of tlb_get_level
Date:   Wed, 23 Jun 2021 15:00:18 +0100
Message-Id: <162444629282.759882.14655008602043376684.b4-ty@kernel.org>
In-Reply-To: <b80ead47-1f88-3a00-18e1-cacc22f54cc4@huawei.com>
References: <b80ead47-1f88-3a00-18e1-cacc22f54cc4@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 23 Jun 2021 15:05:22 +0800, Zhenyu Ye wrote:
> The TTL field indicates the level of page table walk holding the *leaf*
> entry for the address being invalidated. But currently, the TTL field
> may be set to an incorrent value in the following stack:
> 
> pte_free_tlb
>     __pte_free_tlb
>         tlb_remove_table
>             tlb_table_invalidate
>                 tlb_flush_mmu_tlbonly
>                     tlb_flush
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64: tlb: fix the TTL value of tlb_get_level
      https://git.kernel.org/arm64/c/52218fcd61cb

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev