From: "Li,Rongqing" <lirongqing@baidu.com>
To: Yang Shi <yang@os.amperecomputing.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
David Hildenbrand <david@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
"Kevin Brodsky" <kevin.brodsky@arm.com>,
Chaitanya S Prakash <chaitanyas.prakash@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [外部邮件] Re: [PATCH] arm64: mm: refresh stale pmd snapshot after split_contpmd()
Date: Sat, 27 Jun 2026 02:46:21 +0000 [thread overview]
Message-ID: <7ac17ef889d242c29f39898a95364df9@baidu.com> (raw)
In-Reply-To: <32e089d6-7832-4af3-87fc-c1d6bcdb5ba8@os.amperecomputing.com>
>
>
>
> On 6/25/26 4:39 AM, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > split_contpmd() modifies the pmd entries in-place by clearing the CONT
> > bit, but the local 'pmd' variable still holds the old snapshot with
> > CONT set. The subsequent split_pmd() call uses this stale value to
> > derive the pgprot for the new PTE entries via pmd_pgprot(), causing
> > the resulting PTEs to be populated with incorrect protection bits.
>
> If I read the code correctly, CONT bit is cleared by split_pmd(), then the bit
> may be set again for PTEs if we want to have cont ptes. So I don't see any
> problem, did I miss something?
>
You are right, there's no functional issue with the current code.
However, I think explicitly re-reading the pmd is the safer and clearer
approach — it makes the intent obvious (we need the post-modification state)
rather than relying on the implicit assumption that "CONT bit doesn't affect pgprot."
Thanks
[Li,Rongqing]
> Thanks,
> Yang
>
> >
> > Fix this by re-reading the pmd from memory after split_contpmd()
> > returns in both call sites: split_kernel_leaf_mapping_locked() and
> > split_to_ptes_pmd_entry().
> >
> > Fixes: a166563e7ec3 ("arm64: mm: support large block mapping when
> > rodata=full")
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > ---
> > arch/arm64/mm/mmu.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c index
> > 12e862c..e510336 100644
> > --- a/arch/arm64/mm/mmu.c
> > +++ b/arch/arm64/mm/mmu.c
> > @@ -746,8 +746,10 @@ static int
> split_kernel_leaf_mapping_locked(unsigned long addr)
> > if (!pmd_present(pmd))
> > goto out;
> > if (pmd_leaf(pmd)) {
> > - if (pmd_cont(pmd))
> > + if (pmd_cont(pmd)) {
> > split_contpmd(pmdp);
> > + pmd = pmdp_get(pmdp);
> > + }
> > /*
> > * PMD: If addr is PMD aligned then addr already describes a
> > * leaf boundary. Otherwise, split to contpte.
> > @@ -891,8 +893,10 @@ static int split_to_ptes_pmd_entry(pmd_t *pmdp,
> unsigned long addr,
> > int ret = 0;
> >
> > if (pmd_leaf(pmd)) {
> > - if (pmd_cont(pmd))
> > + if (pmd_cont(pmd)) {
> > split_contpmd(pmdp);
> > + pmd = pmdp_get(pmdp);
> > + }
> > ret = split_pmd(pmdp, pmd, gfp, false);
> >
> > /*
prev parent reply other threads:[~2026-06-27 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 11:39 [PATCH] arm64: mm: refresh stale pmd snapshot after split_contpmd() lirongqing
2026-06-26 13:03 ` Dev Jain
2026-06-26 16:03 ` David Hildenbrand (Arm)
2026-06-26 22:53 ` Yang Shi
2026-06-27 2:46 ` Li,Rongqing [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=7ac17ef889d242c29f39898a95364df9@baidu.com \
--to=lirongqing@baidu.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chaitanyas.prakash@arm.com \
--cc=david@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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