From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Robert Dinse <nanook@eskimo.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: Subject: Regression: CONFIG_ASYNC_KERNEL_PGTABLE_FREE causes memory exhaustion and stalls on busy Cascade Lake server (6.18.7 only)
Date: Sun, 1 Feb 2026 19:16:43 +0100 [thread overview]
Message-ID: <e3759678-0b2b-4236-abb8-a16ffc81d4d7@kernel.org> (raw)
In-Reply-To: <06843c7a-909b-41e5-9359-2be51cf9dffa@eskimo.com>
Le 29/01/2026 à 07:10, Robert Dinse a écrit :
>
>
> Reverting to 6.18.6 immediately restores the previous stable behavior.
>
> Attempt to disable CONFIG_ASYNC_KERNEL_PGTABLE_FREE
> ---------------------------------------------------
> I attempted to disable the new async kernel page table freeing feature:
>
> - The symbol `CONFIG_ASYNC_KERNEL_PGTABLE_FREE` appears in `.config`
> - However, it does not appear in xconfig or other configuration frontends
> - Manually editing `.config` to disable it works only until the next
> `make`:
> - As soon as I re-run the build, the option is silently re-enabled
> - I tried to chase the Kconfig dependencies, but the chain was too
> convoluted; it appears to be effectively non-user-selectable and forced
> on by default for my architecture.
>
> From an operator perspective, this feature as currently implemented is
> not workable on a busy machine like this, and the inability to disable
> it makes it difficult to bisect or run with a known-good configuration.
>
Try reverting commit 9f0a7ab700f8 ("iommu/sva: invalidate stale IOTLB
entries for kernel address space") ?
Christophe
next prev parent reply other threads:[~2026-02-01 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 6:10 Robert Dinse
2026-02-01 10:30 ` Thorsten Leemhuis
2026-02-01 18:16 ` Christophe Leroy (CS GROUP) [this message]
2026-02-05 14:04 ` Subject: " Robert Dinse
2026-02-06 4:39 ` Robert Dinse
2026-02-10 2:20 ` Andrew Morton
2026-02-10 2:44 ` Robert Dinse
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=e3759678-0b2b-4236-abb8-a16ffc81d4d7@kernel.org \
--to=chleroy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=nanook@eskimo.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