From: "Jürgen Groß" <jgross@suse.com>
To: "Petr Vaněk" <arkamar@atlas.cz>, linux-kernel@vger.kernel.org
Cc: Kevin Brodsky <kevin.brodsky@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, x86@kernel.org,
xen-devel@lists.xenproject.org, linux-arch@vger.kernel.org
Subject: Re: Regression from a9b3c355c2e6 ("asm-generic: pgalloc: provide generic __pgd_{alloc,free}") with CONFIG_DEBUG_VM_PGFLAGS=y and Xen
Date: Wed, 16 Apr 2025 14:57:49 +0200 [thread overview]
Message-ID: <4347cd96-52c8-4bfc-b383-6fea1554fd4a@suse.com> (raw)
In-Reply-To: <202541612720-Z_-deOZTOztMXHBh-arkamar@atlas.cz>
[-- Attachment #1.1.1: Type: text/plain, Size: 1730 bytes --]
On 16.04.25 14:07, Petr Vaněk wrote:
> Hi all,
>
> I have discovered a regression introduced in commit a9b3c355c2e6
> ("asm-generic: pgalloc: provide generic __pgd_{alloc,free}") [1,2] in
> kernel version 6.14. The problem occurs when the x86 kernel is
> configured with CONFIG_DEBUG_VM_PGFLAGS=y and is run as a PV Dom0 in Xen
> 4.19.1. During the startup, the kernel panics with the error log below.
>
> The commit changed PGD allocation path. In the new implementation
> _pgd_alloc allocates memory with __pgd_alloc, which indirectly calls
>
> alloc_pages_noprof(gfp | __GFP_COMP, order);
>
> This is in contrast to the old behavior, where __get_free_pages was
> used, which indirectly called
>
> alloc_pages_noprof(gfp_mask & ~__GFP_HIGHMEM, order);
>
> The key difference is that the new allocator can return a compound page.
> When xen_pin_page is later called on such a page, it call
> TestSetPagePinned function, which internally uses the PF_NO_COMPOUND
> macro. This macro enforces VM_BUG_ON_PGFLAGS if PageCompound is true,
> triggering the panic when CONFIG_DEBUG_VM_PGFLAGS is enabled.
>
> I am reporting this issue without a patch as I am not sure which part of
> the code should be adapted to resolve the regression.
Thanks for the report AND the analysis.
I believe PMD_ALLOCATION_ORDER needs to be changed: in case the system is
running as a Xen PV domain (or with PTI disabled), PMD_ALLOCATION_ORDER
should be 0.
So I'd suggest to switch PGD_ALLOCATION_ORDER to be defined either as 0
(in case PTI is not configured), or pgd_allocation_order (a new global
variable having the value 0 or 1, depending on PTI active or not).
I'll send a patch.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2025-04-16 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:07 Petr Vaněk
2025-04-16 12:41 ` Matthew Wilcox
2025-04-16 13:53 ` Petr Vaněk
2025-04-16 12:57 ` Jürgen Groß [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=4347cd96-52c8-4bfc-b383-6fea1554fd4a@suse.com \
--to=jgross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=arkamar@atlas.cz \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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