From: Will Deacon <will@kernel.org>
To: Dev Jain <dev.jain@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
muchun.song@linux.dev, osalvador@suse.de, ljs@kernel.org,
david@kernel.org, liam@infradead.org, catalin.marinas@arm.com,
kernel-team@android.com, 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,
apopple@nvidia.com, rcampbell@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, ak@linux.intel.com,
nao.horiguchi@gmail.com, mel@csn.ul.ie, j-nomura@ce.jp.nec.com,
pfalcato@suse.de, tglx@kernel.org, dave.hansen@intel.com,
jpoimboe@kernel.org, linux-arm-kernel@lists.infradead.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v3 0/6] Fix incorrect access of hugetlb pte entries
Date: Wed, 22 Jul 2026 12:52:29 +0100 [thread overview]
Message-ID: <amCu_ei3B3-2OPTB@willie-the-truck> (raw)
In-Reply-To: <4bb234f7-5f3a-452d-92dd-a1e62b6f39aa@arm.com>
On Wed, Jul 22, 2026 at 10:03:04AM +0530, Dev Jain wrote:
> @Will if you could edit the commit message with the following userspace visible
> effect:
>
> "On systems where CONT_PTES != CONT_PMDS (meaning page size is 16K), we could collect
> excess a/d bit state, meaning extra work for the kernel. Even worse, we may iterate
> beyond the PTE table and dereference a garbage ptep pointer to access physical
> memory we don't own. Since the ptep pointer is a linear map address, we may run off
> the end of the linear map, dereference a VA not mapped into the kernel pgtables and
> cause kernel panic."
It's sitting on top of for-next/fixes so I can fold that in, thanks.
Will
next prev parent reply other threads:[~2026-07-22 11:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 11:41 Dev Jain
2026-07-03 11:41 ` [PATCH v3 1/6] arm64: make huge_ptep_get handled unaligned addresses Dev Jain
2026-07-04 2:42 ` Muchun Song
2026-07-05 7:35 ` Andrew Morton
2026-07-05 8:08 ` Dev Jain
2026-07-06 8:45 ` David Hildenbrand (Arm)
2026-07-06 10:52 ` Dev Jain
2026-07-06 10:54 ` Dev Jain
2026-07-06 14:04 ` David Hildenbrand (Arm)
2026-07-16 12:49 ` Will Deacon
2026-07-03 11:41 ` [PATCH v3 2/6] mm/rmap: use huge_ptep_get() in try_to_unmap_one() Dev Jain
2026-07-04 2:44 ` Muchun Song
2026-07-06 8:46 ` David Hildenbrand (Arm)
2026-07-03 11:41 ` [PATCH v3 3/6] mm/rmap: use huge_ptep_get() in try_to_migrate_one() Dev Jain
2026-07-06 8:46 ` David Hildenbrand (Arm)
2026-07-03 11:41 ` [PATCH v3 4/6] mm/migrate: use huge_ptep_get() in remove_migration_pte() Dev Jain
2026-07-03 11:41 ` [PATCH v3 5/6] mm/page_vma_mapped: use huge_ptep_get() for hugetlb Dev Jain
2026-07-03 11:41 ` [PATCH v3 6/6] mm/mprotect: " Dev Jain
2026-07-05 8:33 ` Andrew Morton
2026-07-05 8:47 ` Dev Jain
2026-07-06 8:48 ` David Hildenbrand (Arm)
2026-07-05 7:45 ` [PATCH v3 0/6] Fix incorrect access of hugetlb pte entries Andrew Morton
2026-07-21 17:18 ` Will Deacon
2026-07-21 20:36 ` Andrew Morton
2026-07-22 4:33 ` Dev Jain
2026-07-22 11:52 ` Will Deacon [this message]
2026-07-22 11:30 ` Will Deacon
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=amCu_ei3B3-2OPTB@willie-the-truck \
--to=will@kernel.org \
--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=dev.jain@arm.com \
--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=kernel-team@android.com \
--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=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
all inboxes | Powered by JetHome®