From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Barry Song <baohua@kernel.org>,
Yicong Yang <yangyicong@hisilicon.com>,
Ryan Roberts <ryan.roberts@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64/mm: Close theoretical race where stale TLB entry remains valid
Date: Mon, 2 Jun 2025 14:42:04 +0100 [thread overview]
Message-ID: <174886573625.2942690.14376639867334964612.b4-ty@kernel.org> (raw)
In-Reply-To: <20250530152445.2430295-1-ryan.roberts@arm.com>
On Fri, 30 May 2025 16:23:47 +0100, Ryan Roberts wrote:
> Commit 3ea277194daa ("mm, mprotect: flush TLB if potentially racing with
> a parallel reclaim leaving stale TLB entries") describes a race that,
> prior to the commit, could occur between reclaim and operations such as
> mprotect() when using reclaim's tlbbatch mechanism. See that commit for
> details but the summary is:
>
> """
> Nadav Amit identified a theoritical race between page reclaim and
> mprotect due to TLB flushes being batched outside of the PTL being held.
>
> [...]
Applied to arm64 (for-next/core), thanks!
[1/1] arm64/mm: Close theoretical race where stale TLB entry remains valid
https://git.kernel.org/arm64/c/4b634918384c
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2025-06-02 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 15:23 Ryan Roberts
2025-05-30 22:10 ` Barry Song
2025-06-02 4:59 ` Dev Jain
2025-06-02 8:22 ` Ryan Roberts
2025-06-02 12:00 ` Will Deacon
2025-06-02 14:00 ` Ryan Roberts
2025-06-03 1:55 ` Barry Song
2025-06-02 13:42 ` Will Deacon [this message]
2025-06-03 9:49 ` Barry Song
2025-06-03 10:32 ` Ryan Roberts
2025-06-05 7:59 ` Barry Song
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=174886573625.2942690.14376639867334964612.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=yangyicong@hisilicon.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
all inboxes | Powered by JetHome®