[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191211163201.17179-1-david@redhat.com>
Date: Wed, 11 Dec 2019 17:31:58 +0100
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, David Hildenbrand <david@...hat.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Bob Picco <bob.picco@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Michal Hocko <mhocko@...nel.org>,
Michal Hocko <mhocko@...e.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Oscar Salvador <osalvador@...e.de>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Steven Sistare <steven.sistare@...cle.com>
Subject: [PATCH v2 0/3] mm: fix max_pfn not falling on section boundary
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.
v1 -> v2:
- "mm: fix uninitialized memmaps on a partially populated last section"
-- Refine patch description (esp. how to reproduce), add tested-by
- "fs/proc/page.c: allow inspection of last section and fix end detection"
-- Make it compile for !CONFIG_SPARSE and add a comment to the new
helper function
David Hildenbrand (3):
mm: fix uninitialized memmaps on a partially populated last section
fs/proc/page.c: allow inspection of last section and fix end detection
mm: initialize memmap of unavailable memory directly
fs/proc/page.c | 30 +++++++++++++++++++++++++++---
include/linux/mm.h | 6 ------
mm/page_alloc.c | 43 ++++++++++++++++++++++++++++++++-----------
3 files changed, 59 insertions(+), 20 deletions(-)
--
2.23.0
Powered by blists - more mailing lists