From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, jic23@kernel.org,
Richard Cheng <icheng@nvidia.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
ryan.roberts@arm.com, ardb@kernel.org, kevin.brodsky@arm.com,
anshuman.khandual@arm.com, yang@os.amperecomputing.com,
chaitanyas.prakash@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
newtonl@nvidia.com, kristinc@nvidia.com, mochs@nvidia.com,
kaihengf@nvidia.com, kobak@nvidia.com
Subject: Re: [PATCH v2] arm64/mm: Check the requested PFN range during memory removal
Date: Tue, 21 Jul 2026 18:18:39 +0100 [thread overview]
Message-ID: <178464727167.1304664.6289495269821621329.b4-ty@kernel.org> (raw)
In-Reply-To: <20260721100026.10408-1-icheng@nvidia.com>
On Tue, 21 Jul 2026 18:00:26 +0800, Richard Cheng wrote:
> prevent_memory_remove_notifier() advances pfn while scanning the requested
> range for early memory. When the loop completes, pfn is at or beyond
> end_pfn. Passing it to can_unmap_without_split() therefore checks a range
> after the one being offlined.
>
> Consequently, a valid request can be rejected based on the following
> range, while a request that would split a leaf mapping can be accepted if
> the shifted range can be unmapped without a split. This was observed with
> CXL DAX memory, where the final memory block was incorrectly allowed to
> be offlined.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: Check the requested PFN range during memory removal
https://git.kernel.org/arm64/c/285f90a4d1141
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-07-21 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 10:00 Richard Cheng
2026-07-21 17:18 ` 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=178464727167.1304664.6289495269821621329.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chaitanyas.prakash@arm.com \
--cc=icheng@nvidia.com \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kernel-team@android.com \
--cc=kevin.brodsky@arm.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=newtonl@nvidia.com \
--cc=ryan.roberts@arm.com \
--cc=yang@os.amperecomputing.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®