[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DS7PR11MB6077389EC65455200379F872FC989@DS7PR11MB6077.namprd11.prod.outlook.com>
Date: Thu, 13 Apr 2023 00:47:37 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Mike Kravetz <mike.kravetz@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>
CC: Liu Shixin <liushixin2@...wei.com>,
Naoya Horiguchi <naoya.horiguchi@....com>,
Miaohe Lin <linmiaohe@...wei.com>,
Muchun Song <muchun.song@...ux.dev>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH -next] mm: hwpoison: support recovery from HugePage
copy-on-write faults
> I do not think cc:stable is necessary/desirable. Why?
>
> a873dfe1032a was an enhancement to better handle copying pages with memory
> errors in the kernel. IIUC, we never handled that situation in the past.
> I would not call the fact that it did not take hugetlb into account a bug.
> Although, some might argue that it should have addressed all callers of
> copy_user_highpage which would have included hugetlb. IMO, There would be
> little to gain by backporing to 6.1 as the issue of copying pages with
> errors has existed forever. Perhaps Tony will comment as I was not involved
> in a873dfe1032a.
I concur. We are gradually fixing more cases where Linux consumes
poison data in kernel context. But this is an incremental process to
improve overall reliability. Backporting to stable and long term releases
isn't a priority.
-Tony
Powered by blists - more mailing lists