From: Andrew Morton <akpm@linux-foundation.org>
To: William Tambe <williamt@cadence.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jcmvbkbc@gmail.com" <jcmvbkbc@gmail.com>
Subject: Re: [PATCH] mm/highmem: fix __kmap_to_page() build error
Date: Fri, 16 Jan 2026 09:48:15 -0800 [thread overview]
Message-ID: <20260116094815.ca8ef0ad407a4b8612845d8e@linux-foundation.org> (raw)
In-Reply-To: <SJ0PR07MB86317E00EC0C59DA60935FDCD18DA@SJ0PR07MB8631.namprd07.prod.outlook.com>
On Fri, 16 Jan 2026 17:18:21 +0000 William Tambe <williamt@cadence.com> wrote:
> >From 706fa431358390713c47667f6bcaecce56d071cc Mon Sep 17 00:00:00 2001
> From: William Tambe <williamt@cadence.com>
> Date: Thu, 11 Dec 2025 12:38:19 -0800
> Subject: [PATCH] mm/highmem: fix __kmap_to_page() build error
>
> This changes fixes following build error which is probably a miss from:
> ef6e06b2ef87 highmem: fix kmap_to_page() for kmap_local_page() addresses
>
> mm/highmem.c:184:66: error: 'pteval' undeclared (first use in this
> function); did you mean 'pte_val'?
> 184 | idx = arch_kmap_local_map_idx(i, pte_pfn(pteval));
>
> In __kmap_to_page(), pteval is used but does not exist in the function.
>
> ...
>
> --- a/mm/highmem.c
> +++ b/mm/highmem.c
> @@ -180,12 +180,13 @@ struct page *__kmap_to_page(void *vaddr)
> for (i = 0; i < kctrl->idx; i++) {
> unsigned long base_addr;
> int idx;
> + pte_t pteval = kctrl->pteval[i];
>
> idx = arch_kmap_local_map_idx(i, pte_pfn(pteval));
> base_addr = __fix_to_virt(FIX_KMAP_BEGIN + idx);
>
> if (base_addr == base)
> - return pte_page(kctrl->pteval[i]);
> + return pte_page(pteval);
> }
> }
lgtm, thanks. Seems to affect only xtensa?
I wonder why it took three years to find this.
next prev parent reply other threads:[~2026-01-16 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 17:18 William Tambe
2026-01-16 17:48 ` Andrew Morton [this message]
2026-01-16 17:59 ` William Tambe
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=20260116094815.ca8ef0ad407a4b8612845d8e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=williamt@cadence.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