[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7867c162-6a2e-4291-ac57-a7bb6df5c4ce@huawei.com>
Date: Mon, 20 Jan 2025 17:06:37 +0800
From: mawupeng <mawupeng1@...wei.com>
To: <linmiaohe@...wei.com>
CC: <mawupeng1@...wei.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <akpm@...ux-foundation.org>,
<david@...hat.com>, <osalvador@...e.de>, <nao.horiguchi@...il.com>,
<mhocko@...e.com>
Subject: Re: [PATCH v2 1/3] mm: memory-failure: update ttu flag inside
unmap_poisoned_folio
On 2025/1/20 14:24, Miaohe Lin wrote:
> On 2025/1/16 14:16, Wupeng Ma wrote:
>> From: Ma Wupeng <mawupeng1@...wei.com>
>
> Thanks for your patch. Some nits below.
>
>>
>> Commit 6da6b1d4a7df ("mm/hwpoison: convert TTU_IGNORE_HWPOISON to
>> TTU_HWPOISON") introduce TTU_HWPOISON to replace TTU_IGNORE_HWPOISON
>> in order to stop send SIGBUS signal when accessing an error page after
>> a memory error on a clean folio. However during page migration, anon
>> folio must be set with TTU_HWPOISON during unmap_*(). For pagecache
>> we need some policy just like the one in hwpoison_user_mappings to
>> set this flag. So move this policy from hwpoison_user_mappings to
>> unmap_poisoned_folio to handle this waring properly.
>
> s/waring/warning/g
Thanks for your reply.
will be fixed later.
>
>>
>> Waring will be produced during unamp poison folio with the following log:
>
> s/Waring/Warning/g
Thanks for your reply.
will be fixed later.
Powered by blists - more mailing lists