From: Asahi Lina <lina@asahilina.net>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Subject: LPA2 on non-LPA2 hardware broken with 16K pages
Date: Thu, 18 Jul 2024 18:39:10 +0900 [thread overview]
Message-ID: <50360968-13fb-4e6f-8f52-1725b3177215@asahilina.net> (raw)
Hi,
I ran into this with the Asahi Linux downstream kernel, based on v6.9.9,
but I believe the problem is also still upstream. The issue seems to be
an interaction between folding one page table level at compile time and
another one at runtime.
With this config, we have:
CONFIG_PGTABLE_LEVELS=4
PAGE_SHIFT=14
PMD_SHIFT=25
PUD_SHIFT=36
PGDIR_SHIFT=47
pgtable_l5_enabled() == false (compile time)
pgtable_l4_enabled() == false (runtime, due to no LPA2)
With p4d folded at compile-time, and pud folded at runtime when LPA2 is
not supported.
With this setup, pgd_offset() is broken since the pgd is actually
supposed to become a pud but the shift is wrong, as it is set at compile
time:
#define pgd_index(a) (((a) >> PGDIR_SHIFT) & (PTRS_PER_PGD - 1))
static inline pgd_t *pgd_offset_pgd(pgd_t *pgd, unsigned long address)
{
return (pgd + pgd_index(address));
};
Then we follow the gup logic (abbreviated):
gup_pgd_range:
pgdp = pgd_offset(current->mm, addr);
pgd_t pgd = READ_ONCE(*pgdp);
At this point, pgd is just the 0th entry of the top level page table
(since those extra address bits will always be 0 for valid 47-bit user
addresses).
p4d then gets folded via pgtable-nop4d.h:
gup_p4d_range:
p4dp = p4d_offset_lockless(pgdp, pgd, addr);
= p4d_offset(&(pgd), address)
= &pgd
p4d_t p4d = READ_ONCE(*p4dp);
Now we have p4dp = stack address of pgd, and p4d = pgd.
gup_pud_range:
pudp = pud_offset_lockless(p4dp, p4d, addr);
-> if (!pgtable_l4_enabled())
= p4d_to_folded_pud(p4dp, addr);
= (pud_t *)PTR_ALIGN_DOWN(p4dp, PAGE_SIZE) + pud_index(addr);
pud_t pud = READ_ONCE(*pudp);
Which is bad pointer math because it only works if p4dp points to a real
page table entry inside a page table, not a single u64 stack address.
This causes random oopses in internal_get_user_pages_fast and related
codepaths.
~~ Lina
next reply other threads:[~2024-07-18 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 9:39 Asahi Lina [this message]
2024-07-18 13:14 ` Will Deacon
2024-07-18 13:21 ` Dev Jain
2024-07-18 14:34 ` Asahi Lina
2024-07-19 18:02 ` Ard Biesheuvel
2024-07-23 14:52 ` Will Deacon
2024-07-23 15:02 ` Ard Biesheuvel
2024-07-23 16:05 ` Will Deacon
2024-07-23 16:28 ` Ard Biesheuvel
2024-07-24 11:33 ` Will Deacon
2024-07-24 12:10 ` Ard Biesheuvel
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=50360968-13fb-4e6f-8f52-1725b3177215@asahilina.net \
--to=lina@asahilina.net \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will@kernel.org \
/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