| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <d90050b7-97e7-3975-8918-43350e93d01c@oracle.com>
Date: Mon, 14 Mar 2022 11:41:59 -0700
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Miaohe Lin <linmiaohe@...wei.com>,
Naoya Horiguchi <naoya.horiguchi@...ux.dev>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Yang Shi <shy828301@...il.com>,
Naoya Horiguchi <naoya.horiguchi@....com>,
linux-kernel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH v2] mm/hwpoison: set PageHWPoison after taking page lock
in memory_failure_hugetlb()
On 3/14/22 00:10, Miaohe Lin wrote:
> On 2022/3/14 10:13, Naoya Horiguchi wrote:
>> From: Naoya Horiguchi <naoya.horiguchi@....com>
>>
>> There is a race condition between memory_failure_hugetlb() and hugetlb
>> free/demotion, which causes setting PageHWPoison flag on the wrong page
>> (which was a hugetlb when memory_failure() was called, but was removed
>> or demoted when memory_failure_hugetlb() is called). This results in
>> killing wrong processes. So set PageHWPoison flag with holding page lock,
>
> It seems hold page lock could not help solve this race condition as hugetlb
> page demotion is not required to hold the page lock. Could you please explain
> this a bit more?
I think it would be 'more safe' to SetPageHWPoison on hugetlb head page when
holding hugetlb_lock. I know that does not fit with the way memory error
handling works in general. Just a thought.
--
Mike Kravetz
>
> BTW:Is there some words missing or here should be 'page lock.' instead of 'page lock,' ?
>
>>
>> The actual user-visible effect might be obscure because even if
>> memory_failure() works as expected, some random process could be killed.
>> Even worse, the actual error is left unhandled, so no one prevents later
>> access to it, which might lead to more serious results like consuming
>> corrupted data.
>>
>> This patch depends on Miaohe's patch titled "mm/memory-failure.c: fix
>> race with changing page compound again".
>>
>> Reported-by: Mike Kravetz <mike.kravetz@...cle.com>
>> Signed-off-by: Naoya Horiguchi <naoya.horiguchi@....com>
>> Cc: <stable@...r.kernel.org>
>> ---
>> ChangeLog v1 -> v2:
>> - pass subpage to get_hwpoison_huge_page() instead of head page.
>> - call compound_head() in hugetlb_lock to avoid race with hugetlb
>> demotion/free.
>> ---
>> mm/hugetlb.c | 8 +++++---
>> mm/memory-failure.c | 33 +++++++++++++++------------------
>> 2 files changed, 20 insertions(+), 21 deletions(-)
>>
>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>> index f294db835f4b..345fed90842e 100644
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -6761,14 +6761,16 @@ bool isolate_huge_page(struct page *page, struct list_head *list)
>>
>> int get_hwpoison_huge_page(struct page *page, bool *hugetlb)
>> {
>> + struct page *head;
>> int ret = 0;
>>
>> *hugetlb = false;
>> spin_lock_irq(&hugetlb_lock);
>> - if (PageHeadHuge(page)) {
>> + head = compound_head(page);
>> + if (PageHeadHuge(head)) {
>> *hugetlb = true;
>> - if (HPageFreed(page) || HPageMigratable(page))
>> - ret = get_page_unless_zero(page);
>> + if (HPageFreed(head) || HPageMigratable(head))
>> + ret = get_page_unless_zero(head);
>> else
>> ret = -EBUSY;
>> }
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index a9bfd04d2a3c..c40c00c3a261 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -1193,7 +1193,7 @@ static int __get_hwpoison_page(struct page *page, unsigned long flags)
>> int ret = 0;
>> bool hugetlb = false;
>>
>> - ret = get_hwpoison_huge_page(head, &hugetlb);
>> + ret = get_hwpoison_huge_page(page, &hugetlb);
>> if (hugetlb)
>> return ret;
>>
>> @@ -1280,11 +1280,10 @@ static int get_any_page(struct page *p, unsigned long flags)
>>
>> static int __get_unpoison_page(struct page *page)
>> {
>> - struct page *head = compound_head(page);
>> int ret = 0;
>> bool hugetlb = false;
>>
>> - ret = get_hwpoison_huge_page(head, &hugetlb);
>> + ret = get_hwpoison_huge_page(page, &hugetlb);
>> if (hugetlb)
>> return ret;
>>
>> @@ -1503,24 +1502,11 @@ static int memory_failure_hugetlb(unsigned long pfn, int flags)
>> int res;
>> unsigned long page_flags;
>>
>> - if (TestSetPageHWPoison(head)) {
>> - pr_err("Memory failure: %#lx: already hardware poisoned\n",
>> - pfn);
>> - res = -EHWPOISON;
>> - if (flags & MF_ACTION_REQUIRED)
>> - res = kill_accessing_process(current, page_to_pfn(head), flags);
>> - return res;
>> - }
>> -
>> - num_poisoned_pages_inc();
>> -
>> if (!(flags & MF_COUNT_INCREASED)) {
>> res = get_hwpoison_page(p, flags);
>> if (!res) {
>
> In this (res == 0) case, hugetlb page could be dissolved via __page_handle_poison.
> But since PageHWPoison is not set yet, we can't set the PageHWPoison to the correct
> page. Think about the below code in dissolve_free_huge_page:
> /*
> * Move PageHWPoison flag from head page to the raw
> * error page, which makes any subpages rather than
> * the error page reusable.
> */
> if (PageHWPoison(head) && page != head) {
> SetPageHWPoison(page);
> ClearPageHWPoison(head);
> }
>
> SetPageHWPoison won't be called for the error page. Or am I miss something?
>
>> lock_page(head);
>> if (hwpoison_filter(p)) {
>> - if (TestClearPageHWPoison(head))
>> - num_poisoned_pages_dec();
>> unlock_page(head);
>> return -EOPNOTSUPP;
>> }
>> @@ -1553,13 +1539,16 @@ static int memory_failure_hugetlb(unsigned long pfn, int flags)
>> page_flags = head->flags;
>>
>> if (hwpoison_filter(p)) {
>> - if (TestClearPageHWPoison(head))
>> - num_poisoned_pages_dec();
>> put_page(p);
>> res = -EOPNOTSUPP;
>> goto out;
>> }
>>
>> + if (TestSetPageHWPoison(head))
>> + goto already_hwpoisoned;
>> +
>> + num_poisoned_pages_inc();
>> +
>> /*
>> * TODO: hwpoison for pud-sized hugetlb doesn't work right now, so
>> * simply disable it. In order to make it work properly, we need
>> @@ -1585,6 +1574,14 @@ static int memory_failure_hugetlb(unsigned long pfn, int flags)
>> out:
>> unlock_page(head);
>> return res;
>> +already_hwpoisoned:
>> + put_page(p);
>> + unlock_page(head);
>
> Generally speaking, we should do unlock_page before put_page or page might be disappeared
> before we unlock the page. This should be ok when memory_failure succeeds to handle the
> page previously as it holds one extra page refcnt. But it might be problematic when
> memory_failure failed to handle the page last time. We might be the last user here.
>
>> + pr_err("Memory failure: %#lx: already hardware poisoned\n", pfn);
>> + res = -EHWPOISON;
>> + if (flags & MF_ACTION_REQUIRED)
>> + res = kill_accessing_process(current, page_to_pfn(head), flags);
>> + return res;
>> }
>>
>> static int memory_failure_dev_pagemap(unsigned long pfn, int flags,
>>
>
> Many thanks for your path! :)
Powered by blists - more mailing lists