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 [thread overview]
Message-ID: <162444629282.759882.14655008602043376684.b4-ty@kernel.org> (raw)
In-Reply-To: <b80ead47-1f88-3a00-18e1-cacc22f54cc4@huawei.com>
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
prev parent reply other threads:[~2021-06-23 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 7:05 Zhenyu Ye
2021-06-23 11:04 ` Will Deacon
2021-06-23 11:28 ` Catalin Marinas
2021-06-24 1:55 ` Zhenyu Ye
2021-06-24 8:29 ` Will Deacon
2021-06-23 14:00 ` Will Deacon [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=162444629282.759882.14655008602043376684.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=huyaqin1@huawei.com \
--cc=kernel-team@android.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=maz@kernel.org \
--cc=peterz@infradead.org \
--cc=steven.price@arm.com \
--cc=xiexiangyou@huawei.com \
--cc=yezhenyu2@huawei.com \
--cc=zhurui3@huawei.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