From: "Luck, Tony" <tony.luck@intel.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>, Jiaqi Yan <jiaqiyan@google.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"david@redhat.com" <david@redhat.com>,
"lorenzo.stoakes@oracle.com" <lorenzo.stoakes@oracle.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"ziy@nvidia.com" <ziy@nvidia.com>,
"baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"npache@redhat.com" <npache@redhat.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"dev.jain@arm.com" <dev.jain@arm.com>,
"baohua@kernel.org" <baohua@kernel.org>,
"nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
"Chen, Farrah" <farrah.chen@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Andrew Zaborowski" <andrew.zaborowski@intel.com>
Subject: RE: [PATCH 1/1] mm: prevent poison consumption when splitting THP
Date: Mon, 29 Sep 2025 15:51:46 +0000 [thread overview]
Message-ID: <SJ1PR11MB608350E5169EE77F86A51E2FFC1BA@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SA1PR11MB7130ABC25E060D2CC4749E45891BA@SA1PR11MB7130.namprd11.prod.outlook.com>
> Miaohe mentioned in another e-mail that there was an HWPoisoned flag for the raw error 4K page.
> We could use that flag just to skip that raw error page and still use the zeropage for other
> healthy sub-pages. I'll try that.
That HWPoisoned flag is only set for raw pages where an error has been detected. Maybe Linux
could implement an "is_this_page_all_zero_mc_safe()"[1] that would catch undetected poison and
avoid a crash in that case too?
-Tony
[1] terrible name, pick something better.
next prev parent reply other threads:[~2025-09-29 15:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 3:28 Qiuxu Zhuo
2025-09-28 21:55 ` Jiaqi Yan
2025-09-29 12:29 ` Miaohe Lin
2025-09-29 13:57 ` Zhuo, Qiuxu
2025-09-29 15:15 ` Jiaqi Yan
2025-09-29 13:27 ` Zhuo, Qiuxu
2025-09-29 15:51 ` Luck, Tony [this message]
2025-09-29 16:30 ` Zhuo, Qiuxu
2025-09-29 17:25 ` David Hildenbrand
2025-09-30 1:48 ` Lance Yang
2025-09-30 8:53 ` David Hildenbrand
2025-09-30 10:13 ` Lance Yang
2025-09-30 10:20 ` Lance Yang
2025-09-29 7:34 ` David Hildenbrand
2025-09-29 13:52 ` Zhuo, Qiuxu
2025-09-29 16:12 ` David Hildenbrand
2025-10-12 1:37 ` Wei Yang
2025-10-12 4:23 ` Jiaqi Yan
2025-10-11 7:55 ` [PATCH v2 " Qiuxu Zhuo
2025-10-11 9:09 ` Lance Yang
2025-10-11 18:18 ` Andrew Morton
2025-10-12 1:23 ` Wei Yang
2025-10-13 17:15 ` Zi Yan
2025-10-14 2:42 ` Miaohe Lin
2025-10-14 14:19 ` [PATCH v3 " Qiuxu Zhuo
2025-10-14 14:29 ` David Hildenbrand
2025-10-14 14:51 ` Zhuo, Qiuxu
2025-10-15 6:49 ` [PATCH v4 " Qiuxu Zhuo
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=SJ1PR11MB608350E5169EE77F86A51E2FFC1BA@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.zaborowski@intel.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=farrah.chen@intel.com \
--cc=jiaqiyan@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=nao.horiguchi@gmail.com \
--cc=npache@redhat.com \
--cc=qiuxu.zhuo@intel.com \
--cc=ryan.roberts@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox