From: Jonathan Cameron <jic23@kernel.org>
To: Richard Cheng <icheng@nvidia.com>
Cc: catalin.marinas@arm.com, 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] arm64/mm: Check the requested PFN range during memoroy removal
Date: Mon, 20 Jul 2026 21:23:06 +0100 [thread overview]
Message-ID: <20260720212306.674bd0d1@jic23-huawei> (raw)
In-Reply-To: <20260720020655.9607-1-icheng@nvidia.com>
On Mon, 20 Jul 2026 10:06:55 +0800
Richard Cheng <icheng@nvidia.com> wrote:
Hi Richard,
Please run a spell checker over your commit messages.
"memory" in the patch description for example.
Fix itself looks correct to me.
> prevent_memory_remove_notifier() advances pfn while checking whether the
> range contains early memory. After the loop, pfn points to end_pfn, but
> it is passed to can_unmap_without_split(). This checks the range
> immediately after the requested memory instead of the range being
> offlined.
>
> Consequently, valid requests can be rejected with shifted address range,
> while an unsafe request can be accepted when the following range is
> unmapped. This was observed with CXL DAX memory, where the final memory
> block was incorrectly allowed offline.
>
> Pass arg->start_pfn so the leaf-split check examines the requested
> range.
>
> Fixes: 95a58852b0e5 ("arm64/mm: Reject memory removal that splits a kernel leaf mapping")
> Signed-off-by: Richard Cheng <icheng@nvidia.com>
> ---
> The bug occurred on a machine with CXL Type-3 device.
> Branch: cxl-next
>
> Before 95a58852b0e5:
>
> """
> $ sudo echo offline > memory557056/state
> write error: Operation not permitted
> $ sudo dmesg
> ---[snip]---
> [440008000000 440010000000] splits a leaf entry in linear map
>
> $ sudo echo offline > memory558079/state
> $ cat memory558079/state
> offline
> """
>
> After:
> """
> $ sudo echo offline > memory557056/state
> write error: Operation not permitted
> [440000000000 440008000000] splits a leaf entry in linear map
>
> $ sudo echo offline > memory558079/state
> write error: Operation not permitted
> [441ff8000000 442000000000] splits a leaf entry in linear map
>
> My fix corrects the checked range and prevents the false acceptance.
>
> Best regards,
> Richard Cheng.
> ---
> arch/arm64/mm/mmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> index a25d8beacc83..18a8b0d3714e 100644
> --- a/arch/arm64/mm/mmu.c
> +++ b/arch/arm64/mm/mmu.c
> @@ -2194,7 +2194,7 @@ static int prevent_memory_remove_notifier(struct notifier_block *nb,
> }
> }
>
> - if (!can_unmap_without_split(pfn, arg->nr_pages))
> + if (!can_unmap_without_split(arg->start_pfn, arg->nr_pages))
> return NOTIFY_BAD;
>
> return NOTIFY_OK;
>
> base-commit: 5ca04f3ba91f1773bbd5da6d9c654ccc1ba7831d
prev parent reply other threads:[~2026-07-20 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 2:06 [PATCH] arm64/mm: Check the requested PFN range during memoroy removal Richard Cheng
2026-07-20 3:56 ` Anshuman Khandual
2026-07-20 20:23 ` Jonathan Cameron [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=20260720212306.674bd0d1@jic23-huawei \
--to=jic23@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=kaihengf@nvidia.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=will@kernel.org \
--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