From: Andrew Morton <akpm@linux-foundation.org>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: Balbir Singh <balbirs@nvidia.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"David Hildenbrand (Red Hat)" <davidhildenbrandkernel@gmail.com>,
Jan Polensky <japo@linux.ibm.com>,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
will@kernel.org
Subject: Re: [PATCH] mm/huge_memory: restrict __GFP_ZEROTAGS to HW tagging architectures
Date: Mon, 24 Nov 2025 10:08:16 -0800 [thread overview]
Message-ID: <20251124100816.a4f16b6a84bae7c97dfc21fb@linux-foundation.org> (raw)
In-Reply-To: <e83945be-056a-443c-b140-e3301c2109c5@kernel.org>
On Mon, 24 Nov 2025 11:57:09 +0100 "David Hildenbrand (Red Hat)" <david@kernel.org> wrote:
> > I've run into the issue where due to init being set to false if zero_tags was set,
> > the system does not clear the zero_folio. I just spent a lot of time debugging it :)
> >
> > Catalin, were you going to send out this patch as a fix to be included in mm-unstable?
> > I've for now reverted your __GFP_ZEROTAGS change to get_huge_zero_folio() for my testing
> >
> > I am on the current mm-new branch.
>
> We have a fix upstream now:
>
> commit 5bebe8de19264946d398ead4e6c20c229454a552
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Nov 18 08:21:27 2025 -0800
>
> mm/huge_memory: Fix initialization of huge zero folio
>
>
> Andrew could consider picking it up as well temporarily to fix the issue
> until we rebase on top of the new kernel.
Sure, I added 5bebe8de19264946d398ead4e6c20c229454a552 to mm-new as a
temp thing.
next prev parent reply other threads:[~2025-11-24 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:57 [PATCH] mm/huge_memory: Initialise the tags of the huge zero folio Catalin Marinas
2025-10-31 17:15 ` David Hildenbrand
2025-11-03 13:32 ` Mark Brown
2025-11-03 14:30 ` Catalin Marinas
2025-11-03 14:41 ` David Hildenbrand (Red Hat)
2025-11-03 15:59 ` Catalin Marinas
2025-11-03 19:29 ` Beleswar Prasad Padhi
2025-11-04 1:05 ` Andrew Morton
2025-11-04 8:52 ` Catalin Marinas
2025-11-04 11:53 ` [PATCH] mm/huge_memory: Initialise the tags of the huge zero Lance Yang
2025-11-08 19:19 ` [PATCH] mm/huge_memory: initialise the tags of the huge zero folio Jan Polensky
2025-11-09 0:42 ` [PATCH] Clarification: please ignore earlier submission Jan Polensky
2025-11-09 0:36 ` [PATCH] mm/huge_memory: restrict __GFP_ZEROTAGS to HW tagging architectures Jan Polensky
2025-11-10 9:09 ` David Hildenbrand (Red Hat)
2025-11-10 9:48 ` Jan Polensky
2025-11-10 9:53 ` David Hildenbrand (Red Hat)
2025-11-10 15:28 ` Catalin Marinas
2025-11-10 15:55 ` Catalin Marinas
2025-11-22 12:04 ` Balbir Singh
2025-11-24 10:57 ` David Hildenbrand (Red Hat)
2025-11-24 18:08 ` Andrew Morton [this message]
2025-11-11 10:44 ` Jan Polensky
2025-11-11 12:27 ` David Hildenbrand (Red Hat)
2025-11-11 12:28 ` David Hildenbrand (Red Hat)
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=20251124100816.a4f16b6a84bae7c97dfc21fb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=davidhildenbrandkernel@gmail.com \
--cc=japo@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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