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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 13 Aug 2020 09:07:44 +0200
From:   Michal Hocko <>
To:     David Hildenbrand <>
Cc:     Charan Teja Reddy <>,,,,,
Subject: Re: [PATCH] mm, page_alloc: fix core hung in free_pcppages_bulk()

On Tue 11-08-20 10:29:24, David Hildenbrand wrote:
> I was wondering if we should rather set all pageblocks to
> MIGRATE_ISOLATE in online_pages() before doing the online_pages_range()
> call, and do undo_isolate_page_range() after onlining is done.
> move_pfn_range_to_zone()->memmap_init_zone() marks all pageblocks
> MIGRATE_MOVABLE, and as that function is used also during boot, we could
> supply a parameter to configure this.
> This would prevent another race from happening: Having pages exposed to
> the buddy ready for allocation in online_pages_range() before the
> sections are marked online.
> This would avoid any pages from getting allocated before we're
> completely done onlining.

This sounds like a reasonable idea to me.


We already do depend on the memory isolation in the hotremove. Doing the
same for hotplug in general makes sense as well.

Michal Hocko

Powered by blists - more mailing lists