From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Dev Jain <dev.jain@arm.com>, catalin.marinas@arm.com, will@kernel.org
Cc: ryan.roberts@arm.com, rppt@kernel.org,
shijie@os.amperecomputing.com, yang@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] arm64/pageattr: Propagate return value from __change_memory_common
Date: Mon, 3 Nov 2025 13:18:11 +0530 [thread overview]
Message-ID: <7d4d0d6a-390d-48d6-ba2a-7adfac2e30ca@arm.com> (raw)
In-Reply-To: <20251103061306.82034-1-dev.jain@arm.com>
On 03/11/25 11:43 AM, Dev Jain wrote:
> Post a166563e7ec3 ("arm64: mm: support large block mapping when rodata=full"),
> __change_memory_common has a real chance of failing due to split failure.
> Before that commit, this line was introduced in c55191e96caa, still having
A small nit:
Commit description needs to follow after the SHA ID ^^^^^^^^^^
> a chance of failing if it needs to allocate pagetable memory in
> apply_to_page_range, although that has never been observed to be true.
> In general, we should always propagate the return value to the caller.
>
> Cc: stable@vger.kernel.org
> Fixes: c55191e96caa ("arm64: mm: apply r/o permissions of VM areas to its linear alias as well")
Does is really need a Fixes: ? There is no problem which is being fixed.
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> Based on Linux 6.18-rc4.
>
> arch/arm64/mm/pageattr.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c
> index 5135f2d66958..b4ea86cd3a71 100644
> --- a/arch/arm64/mm/pageattr.c
> +++ b/arch/arm64/mm/pageattr.c
> @@ -148,6 +148,7 @@ static int change_memory_common(unsigned long addr, int numpages,
> unsigned long size = PAGE_SIZE * numpages;
> unsigned long end = start + size;
> struct vm_struct *area;
> + int ret;
> int i;
>
> if (!PAGE_ALIGNED(addr)) {
> @@ -185,8 +186,10 @@ static int change_memory_common(unsigned long addr, int numpages,
> if (rodata_full && (pgprot_val(set_mask) == PTE_RDONLY ||
> pgprot_val(clear_mask) == PTE_RDONLY)) {
> for (i = 0; i < area->nr_pages; i++) {
> - __change_memory_common((u64)page_address(area->pages[i]),
> + ret = __change_memory_common((u64)page_address(area->pages[i]),
> PAGE_SIZE, set_mask, clear_mask);
> + if (ret)
> + return ret;
> }
> }
Although the change does make sense.
next prev parent reply other threads:[~2025-11-03 7:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 6:13 [PATCH] arm64/pageattr: Propagate return value from __change_memory_common Dev Jain
2025-11-03 7:48 ` Anshuman Khandual [this message]
2025-11-03 8:34 ` Dev Jain
2025-11-03 15:16 ` Will Deacon
2025-11-03 18:45 ` Yang Shi
2025-11-04 3:36 ` Dev Jain
2025-11-04 12:56 ` Will Deacon
2025-11-04 13:22 ` Dev Jain
2025-11-05 3:57 ` Dev Jain
2025-11-11 3:39 ` Dev Jain
2025-11-11 4:17 ` Yang Shi
2025-11-11 4:37 ` Dev Jain
2025-11-11 4:44 ` Yang Shi
2025-11-11 4:55 ` Dev Jain
2025-11-11 5:08 ` Yang Shi
2025-11-11 5:12 ` Dev Jain
2025-11-11 17:52 ` Ryan Roberts
2025-11-11 23:59 ` Yang Shi
2025-11-12 3:50 ` Dev Jain
2025-11-11 23:45 ` Yang Shi
2025-11-12 3:47 ` Dev Jain
2025-11-12 5:59 ` Dev Jain
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=7d4d0d6a-390d-48d6-ba2a-7adfac2e30ca@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dev.jain@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shijie@os.amperecomputing.com \
--cc=stable@vger.kernel.org \
--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