[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191009142435.3975-1-david@redhat.com>
Date: Wed, 9 Oct 2019 16:24:33 +0200
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>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Anthony Yznaga <anthony.yznaga@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Michal Hocko <mhocko@...nel.org>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Pankaj gupta <pagupta@...hat.com>, Qian Cai <cai@....pw>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Toshiki Fukasawa <t-fukasawa@...jp.nec.com>
Subject: [PATCH v2 0/2] mm: Don't access uninitialized memmaps in PFN walkers
This is the follow-up of:
[PATCH v1] mm: Fix access of uninitialized memmaps in fs/proc/page.c
We have multiple places where we might access uninitialized memmaps and
trigger kernel BUGs. Make sure to only access initialized memmaps.
Some of these places got easier to trigger with:
[PATCH v6 00/10] mm/memory_hotplug: Shrink zones before removing memory
As memmaps are now also poisoned when memory is offlined, before it is
actually removed.
v1 -> v2:
- Drop ZONE_DEVICE support from the /proc/k... files as requested by Michal
- Further simplify the code
- Split up into two patches
David Hildenbrand (2):
mm: Don't access uninitialized memmaps in fs/proc/page.c
mm/memory-failure.c: Don't access uninitialized memmaps in
memory_failure()
fs/proc/page.c | 28 ++++++++++++++++------------
mm/memory-failure.c | 14 ++++++++------
2 files changed, 24 insertions(+), 18 deletions(-)
--
2.21.0
Powered by blists - more mailing lists