| 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: <20220928012647.GA597297@u2004.lan>
Date: Wed, 28 Sep 2022 10:26:47 +0900
From: Naoya Horiguchi <naoya.horiguchi@...ux.dev>
To: Miaohe Lin <linmiaohe@...wei.com>
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Yang Shi <shy828301@...il.com>,
Oscar Salvador <osalvador@...e.de>,
Muchun Song <songmuchun@...edance.com>,
Jane Chu <jane.chu@...cle.com>,
Naoya Horiguchi <naoya.horiguchi@....com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/4] mm,hwpoison,hugetlb,memory_hotplug: hotremove
memory section with hwpoisoned hugepage
On Sat, Sep 24, 2022 at 07:43:16PM +0800, Miaohe Lin wrote:
> On 2022/9/21 17:13, Naoya Horiguchi wrote:
> > From: Naoya Horiguchi <naoya.horiguchi@....com>
> >
> > HWPoisoned page is not supposed to be accessed once marked, but currently
> > such accesses can happen during memory hotremove because do_migrate_range()
> > can be called before dissolve_free_huge_pages() is called.
> >
> > Clear HPageMigratable for hwpoisoned hugepages to prevent them from being
> > migrated. This should be done in hugetlb_lock to avoid race against
> > isolate_hugetlb().
> >
> > get_hwpoison_huge_page() needs to have a flag to show it's called from
> > unpoison to take refcount of hwpoisoned hugepages, so add it.
> >
> > Reported-by: Miaohe Lin <linmiaohe@...wei.com>
> > Signed-off-by: Naoya Horiguchi <naoya.horiguchi@....com>
>
> Thanks for your work, Naoya. Maybe something to improve below.
>
> > ---
> > ChangeLog v2 -> v3
> > - move to the approach of clearing HPageMigratable instead of shifting
> > dissolve_free_huge_pages.
> > ---
> > include/linux/hugetlb.h | 4 ++--
> > mm/hugetlb.c | 4 ++--
> > mm/memory-failure.c | 12 ++++++++++--
> > 3 files changed, 14 insertions(+), 6 deletions(-)
> >
>
> <snip>
>
> > @@ -7267,7 +7267,7 @@ int get_hwpoison_huge_page(struct page *page, bool *hugetlb)
> > *hugetlb = true;
> > if (HPageFreed(page))
> > ret = 0;
> > - else if (HPageMigratable(page))
> > + else if (HPageMigratable(page) || unpoison)
>
> Is unpoison_memory() expected to restore the HPageMigratable flag as well ?
No it isn't. When unpoison_memory() unpoisons a hugepage, the hugepage
is sent back to free hugepage pool, so I think that there's no need to
restore HPageMigratable for it.
>
> > ret = get_page_unless_zero(page);
> > else
> > ret = -EBUSY;
> > diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> > index 145bb561ddb3..5942e1c0407e 100644
> > --- a/mm/memory-failure.c
> > +++ b/mm/memory-failure.c
> > @@ -1244,7 +1244,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(head, &hugetlb, false);
> > if (hugetlb)
> > return ret;
> >
> > @@ -1334,7 +1334,7 @@ static int __get_unpoison_page(struct page *page)
> > int ret = 0;
> > bool hugetlb = false;
> >
> > - ret = get_hwpoison_huge_page(head, &hugetlb);
> > + ret = get_hwpoison_huge_page(head, &hugetlb, true);
> > if (hugetlb)
> > return ret;
> >
> > @@ -1815,6 +1815,13 @@ int __get_huge_page_for_hwpoison(unsigned long pfn, int flags)
> > goto out;
> > }
> >
> > + /*
> > + * Clearing HPageMigratable for hwpoisoned hugepages to prevent them
> > + * from being migrated by memory hotremove.
> > + */
> > + if (count_increased)
> > + ClearHPageMigratable(head);
>
> I believe this can prevent hwpoisoned hugepages from being migrated though there still be some windows.
I'm not sure of "still racy" part, so could you elaborate it?
Main scenario this patch tries to handle is like below:
CPU 0 CPU 1
get_huge_page_for_hwpoison
// take hugetlb_lock
__get_huge_page_for_hwpoison
scan_movable_pages
if HPageMigratable
goto found
do_migrate_range
if HPageMigratable
get_page_unless_zero
hugetlb_set_page_hwpoison
ClearHPageMigratable
// release hugetlb_lock
isolate_hugetlb
// take hugetlb_lock
if !HPageMigratable
// fails to isolate the hwpoisoned hugetlb.
Maybe the following could be possible.
CPU 0 CPU 1
scan_movable_pages
if HPageMigratable
goto found
do_migrate_range
isolate_hugetlb
// the hugetlb is isolated,
// but it's not hwpoisoned yet.
get_huge_page_for_hwpoison
// take hugetlb_lock
__get_huge_page_for_hwpoison
if HPageMigratable
get_page_unless_zero
hugetlb_set_page_hwpoison
ClearHPageMigratable
// release hugetlb_lock
In this case, the hugepage is maybe broken but not marked as hwpoison yet,
so it's not detectable.
>
> > +
> > return ret;
> > out:
> > if (count_increased)
> > @@ -1862,6 +1869,7 @@ static int try_memory_failure_hugetlb(unsigned long pfn, int flags, int *hugetlb
> >
> > if (hwpoison_filter(p)) {
> > hugetlb_clear_page_hwpoison(head);
> > + SetHPageMigratable(head);
>
> Would we set HPageMigratable flag for free hugetlb pages here? IIUC, they're not expected to have this flag set.
Thank you, you're right. This should be done in "if (res == 1)" block.
(hwpoison_filter often bothers me ...)
>
> Thanks,
> Miaohe Lin
Thank you very much!
- Naoya Horiguchi
Powered by blists - more mailing lists