From: Andrew Morton <akpm@linux-foundation.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: xueyuan.chen@vivo.com, Lorenzo Stoakes <ljs@kernel.org>,
linux-mm@kvack.org, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>, Bob Liu <lliubbo@gmail.com>,
linux-kernel@vger.kernel.org,
Xueyuan Chen <xueyuan.chen21@gmail.com>
Subject: Re: [PATCH] mm/huge_memory: fix huge zero folio publication race
Date: Wed, 29 Jul 2026 18:02:41 -0700 [thread overview]
Message-ID: <20260729180241.2b8bcb2379b975b22c48d251@linux-foundation.org> (raw)
In-Reply-To: <37c40d62-51e2-45b4-9837-a4b96d1640b3@kernel.org>
On Wed, 29 Jul 2026 08:44:12 +0200 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -245,8 +245,11 @@ static bool get_huge_zero_folio(void)
> > }
> > WRITE_ONCE(huge_zero_pfn, folio_pfn(zero_folio));
> >
> > - /* We take additional reference here. It will be put back by shrinker */
> > - atomic_set(&huge_zero_refcount, 2);
> > + /*
> > + * Publish the folio and PFN before making them available to lockless
> > + * users. Pairs with a successful atomic_inc_not_zero() above.
> > + */
> > + atomic_set_release(&huge_zero_refcount, 2);
> > preempt_enable();
> > count_vm_event(THP_ZERO_PAGE_ALLOC);
> > return true;
>
> https://lore.kernel.org/r/20260728-fix-refcounted-huge-zero-v1-0-3f261f5447b4@kernel.org
Does that actually fix the same thing?
Is so, Xueyuan's Fixes: is 97ae17497e99 ("thp: implement refcounting
for huge zero page"). Which to believe?
next prev parent reply other threads:[~2026-07-30 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 4:50 [PATCH] mm/huge_memory: fix huge zero folio publication race xueyuan.chen
2026-07-29 6:44 ` David Hildenbrand (Arm)
2026-07-30 1:02 ` Andrew Morton [this message]
2026-07-30 7:27 ` Lorenzo Stoakes (ARM)
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=20260729180241.2b8bcb2379b975b22c48d251@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lliubbo@gmail.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=xueyuan.chen21@gmail.com \
--cc=xueyuan.chen@vivo.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.