Re: [PATCH v2 0/3] mm: fix max_pfn not falling on section boundary

[Andrew Morton]

On Wed, 11 Dec 2019 17:31:58 +0100 David Hildenbrand <david@xxxxxxxxxx> wrote:

> Playing with different memory sizes for a x86-64 guest, I discovered that
> some memmaps (highest section if max_mem does not fall on the section
> boundary) are marked as being valid and online, but contain garbage. We
> have to properly initialize these memmaps.
> 
> Looking at /proc/kpageflags and friends, I found some more issues,
> partially related to this.

We're still showing very little (ie no) review activity on this
patchset.