[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5202b6fe-7008-6e1b-eaae-03edbe7c055c@huawei.com>
Date: Thu, 13 Apr 2023 09:55:32 +0800
From: Liu Shixin <liushixin2@...wei.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Mike Kravetz <mike.kravetz@...cle.com>
CC: Naoya Horiguchi <naoya.horiguchi@....com>,
Tony Luck <tony.luck@...el.com>,
Miaohe Lin <linmiaohe@...wei.com>,
Muchun Song <muchun.song@...ux.dev>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] mm: hwpoison: support recovery from HugePage
copy-on-write faults
On 2023/4/13 6:56, Andrew Morton wrote:
> On Wed, 12 Apr 2023 15:21:38 -0700 Mike Kravetz <mike.kravetz@...cle.com> wrote:
>
>>>> Commit a873dfe1032a ("mm, hwpoison: try to recover from copy-on write
>>>> faults") introduced the routine copy_user_highpage_mc() to gracefully
>>>> handle copying of user pages with uncorrectable errors. Previously,
>>>> such copies would result in a kernel crash. hugetlb has separate code
>>>> paths for copy-on-write and does not benefit from the changes made in
>>>> commit a873dfe1032a.
>> I was just going to suggest adding the line,
>>
>> Hence, copy-on-write of hugetlb user pages with uncorrectable errors
>> will result in a kernel crash as was the case with 'normal' pages before
>> commit a873dfe1032a.
>>
>> However, I'm guessing it might be more clear if we start with the
>> runtime effects. Something like:
>>
>> copy-on-write of hugetlb user pages with uncorrectable errors will result
>> in a kernel crash. This is because the copy is performed in kernel mode
>> and in general we can not handle accessing memory with such errors while
>> in kernel mode. Commit a873dfe1032a ("mm, hwpoison: try to recover from
>> copy-on write faults") introduced the routine copy_user_highpage_mc() to
>> gracefully handle copying of user pages with uncorrectable errors. However,
>> the separate hugetlb copy-on-write code paths were not modified as part
>> of commit a873dfe1032a.
> Sounds good. So I assume cc:stable is desirable.
>
> I can't actually get the patch to apply to anything. Can we please
> have a redo against current -linus?
OK, I will apply this patch to mainline again.
>
> .
>
Powered by blists - more mailing lists