From: Boudewijn van der Heide <boudewijn@delta-utec.com>
To: ziy@nvidia.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
boudewijn@delta-utec.com, david@redhat.com, duenwen@google.com,
hannes@cmpxchg.org, harry.yoo@oracle.com, jackmanb@google.com,
jane.chu@oracle.com, jiaqiyan@google.com, jthoughton@google.com,
linmiaohe@huawei.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com, mhocko@suse.com,
muchun.song@linux.dev, nao.horiguchi@gmail.com,
osalvador@suse.de, rientjes@google.com, rppt@kernel.org,
surenb@google.com, tony.luck@intel.com, vbabka@suse.cz,
wangkefeng.wang@huawei.com, william.roche@oracle.com,
willy@infradead.org
Subject: Re: [PATCH v4 0/3] Only free healthy pages in high-order has_hwpoisoned folio
Date: Fri, 6 Feb 2026 17:16:28 +0100 [thread overview]
Message-ID: <20260206161628.78161-1-boudewijn@delta-utec.com> (raw)
In-Reply-To: <2C382EC0-0FB7-4882-8B87-E467454178D2@nvidia.com>
Hi Yan, Zi,
> No, split code[1] sets has_hwpoison flag when it split a folio to a non-0 order
> folios. If you do not see it in your kernel code, you might need to update
> your kernel to latest stable one or one newer than or equal to 6.18.
Thanks for pointing out the split code. I went through the callstacks
again and I agree it propagates the flag correctly.
I missed this initially.
Kind regards,
Boudewijn
prev parent reply other threads:[~2026-02-06 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 19:41 Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 1/3] mm/page_alloc: only " Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 2/3] mm/memory-failure: set has_hwpoisoned flags on dissolved HugeTLB folio Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 3/3] mm/memory-failure: skip take_page_off_buddy after dissolving HWPoison HugeTLB page Jiaqi Yan
2026-02-04 15:23 ` [PATCH v4 0/3] Only free healthy pages in high-order has_hwpoisoned folio Boudewijn van der Heide
2026-02-04 15:48 ` Zi Yan
2026-02-06 16:16 ` Boudewijn van der Heide [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=20260206161628.78161-1-boudewijn@delta-utec.com \
--to=boudewijn@delta-utec.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=duenwen@google.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jackmanb@google.com \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=william.roche@oracle.com \
--cc=willy@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox