From: Dev Jain <dev.jain@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
muchun.song@linux.dev, osalvador@suse.de,
akpm@linux-foundation.org, ljs@kernel.org, liam@infradead.org
Cc: riel@surriel.com, vbabka@kernel.org, harry@kernel.org,
jannh@google.com, lance.yang@linux.dev, kas@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rcampbell@nvidia.com, apopple@nvidia.com, ziy@nvidia.com,
matthew.brost@intel.com, joshua.hahnjy@gmail.com,
rakie.kim@sk.com, byungchul@sk.com, gourry@gourry.net,
ying.huang@linux.alibaba.com, j-nomura@ce.jp.nec.com,
nao.horiguchi@gmail.com, ak@linux.intel.com, mel@csn.ul.ie,
pfalcato@suse.de, jpoimboe@kernel.org, dave.hansen@intel.com,
tglx@kernel.org, catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org, ryan.roberts@arm.com,
anshuman.khandual@arm.com
Subject: Re: [PATCH v2 6/6] mm/mprotect: use huge_ptep_get() for hugetlb
Date: Fri, 3 Jul 2026 11:00:32 +0530 [thread overview]
Message-ID: <1ef238fd-232c-4b8a-b28d-cd20db57bcfc@arm.com> (raw)
In-Reply-To: <f1bef34f-987a-4a47-99fb-acdeda1c072d@kernel.org>
On 02/07/26 9:17 pm, David Hildenbrand (Arm) wrote:
> On 7/2/26 07:13, Dev Jain wrote:
>> prot_none_hugetlb_entry() is the hugetlb callback for the early
>> mprotect(PROT_NONE) PFN permission walk on x86.
>>
>> The callback passes the decoded PFN to pfn_modify_allowed(). For a
>> hugetlb callback, the pte pointer refers to a hugetlb entry. On
>> architectures where hugetlb entries need huge_ptep_get(), reading that
>> entry with ptep_get() can make the permission check use the wrong PFN.
>>
>> Use huge_ptep_get() before decoding the hugetlb PFN.
>>
>> Currently there is no path which can trigger a bug: huge_ptep_get() is a
>> simple ptep_get() for x86, and the prot_none walk occurs only for x86.
>>
>> So no need to backport - use the correct helper anyways.
>>
>> Fixes: 42e4089c7890 ("x86/speculation/l1tf: Disallow non privileged high MMIO PROT_NONE mappings")
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>> ---
>> mm/mprotect.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/mprotect.c b/mm/mprotect.c
>> index 9cbf932b028cf..23779632d18bf 100644
>> --- a/mm/mprotect.c
>> +++ b/mm/mprotect.c
>> @@ -699,14 +699,20 @@ static int prot_none_pte_entry(pte_t *pte, unsigned long addr,
>> 0 : -EACCES;
>> }
>>
>> +#ifdef CONFIG_HUGETLB_PAGE
>> static int prot_none_hugetlb_entry(pte_t *pte, unsigned long hmask,
>> unsigned long addr, unsigned long next,
>> struct mm_walk *walk)
>> {
>> - return pfn_modify_allowed(pte_pfn(ptep_get(pte)),
>> + pte_t entry = huge_ptep_get(walk->mm, addr, pte);
>
> Nit: can be const :)
>
>> +
>> + return pfn_modify_allowed(pte_pfn(entry),
>> *(pgprot_t *)(walk->private)) ?
>> 0 : -EACCES;
>
> Indentation is odd.
>
> Can we just make this readable?
>
> if (pfn_modify_allowed ...)
> return 0
> return -EACCESS;
>
Sure I'll do this.
>
prev parent reply other threads:[~2026-07-03 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260702051341.126509-1-dev.jain@arm.com>
[not found] ` <20260702051341.126509-2-dev.jain@arm.com>
2026-07-02 15:28 ` [PATCH v2 1/6] arm64: make huge_ptep_get handled unaligned addresses David Hildenbrand (Arm)
[not found] ` <20260702051341.126509-3-dev.jain@arm.com>
[not found] ` <97a43d82-28c2-4f98-ad74-fe05ed9f0297@linux.dev>
[not found] ` <a6a00b38-612f-439d-9b75-337170e3af30@arm.com>
[not found] ` <CE6E9F6C-8891-40E3-A5B7-BA475070EACD@linux.dev>
2026-07-02 15:30 ` [PATCH v2 2/6] mm/rmap: use huge_ptep_get() in try_to_unmap_one() David Hildenbrand (Arm)
2026-07-02 15:32 ` David Hildenbrand (Arm)
2026-07-03 5:30 ` Dev Jain
2026-07-03 7:06 ` David Hildenbrand (Arm)
[not found] ` <20260702051341.126509-4-dev.jain@arm.com>
2026-07-02 15:34 ` [PATCH v2 3/6] mm/rmap: use huge_ptep_get() in try_to_migrate_one() David Hildenbrand (Arm)
[not found] ` <20260702051341.126509-5-dev.jain@arm.com>
2026-07-02 15:44 ` [PATCH v2 4/6] mm/migrate: use huge_ptep_get() in remove_migration_pte() David Hildenbrand (Arm)
[not found] ` <20260702051341.126509-6-dev.jain@arm.com>
2026-07-02 15:44 ` [PATCH v2 5/6] mm/page_vma_mapped: use huge_ptep_get() for hugetlb David Hildenbrand (Arm)
[not found] ` <20260702051341.126509-7-dev.jain@arm.com>
2026-07-02 15:47 ` [PATCH v2 6/6] mm/mprotect: " David Hildenbrand (Arm)
2026-07-03 5:30 ` Dev Jain [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=1ef238fd-232c-4b8a-b28d-cd20db57bcfc@arm.com \
--to=dev.jain@arm.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=harry@kernel.org \
--cc=j-nomura@ce.jp.nec.com \
--cc=jannh@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=jpoimboe@kernel.org \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=matthew.brost@intel.com \
--cc=mel@csn.ul.ie \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=pfalcato@suse.de \
--cc=rakie.kim@sk.com \
--cc=rcampbell@nvidia.com \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=will@kernel.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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