From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
Dan Williams <dan.j.williams@intel.com>,
Michal Hocko <mhocko@kernel.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Pankaj gupta <pagupta@redhat.com>, Qian Cai <cai@lca.pw>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Toshiki Fukasawa <t-fukasawa@vx.jp.nec.com>
Subject: [PATCH v2 0/2] mm: Don't access uninitialized memmaps in PFN walkers
Date: Wed, 9 Oct 2019 16:24:33 +0200 [thread overview]
Message-ID: <20191009142435.3975-1-david@redhat.com> (raw)
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
next reply other threads:[~2019-10-09 14:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:24 David Hildenbrand [this message]
2019-10-09 14:24 ` [PATCH v2 1/2] mm: Don't access uninitialized memmaps in fs/proc/page.c David Hildenbrand
2019-10-09 14:41 ` Michal Hocko
2019-10-14 8:44 ` David Hildenbrand
2019-10-09 14:24 ` [PATCH v2 2/2] mm/memory-failure.c: Don't access uninitialized memmaps in memory_failure() David Hildenbrand
2019-10-09 14:43 ` Michal Hocko
2019-10-10 7:27 ` David Hildenbrand
2019-10-10 7:35 ` Michal Hocko
2019-10-10 7:52 ` David Hildenbrand
2019-10-10 7:58 ` David Hildenbrand
2019-10-11 6:02 ` Naoya Horiguchi
2019-10-11 10:13 ` David Hildenbrand
2019-10-14 13:36 ` Michal Hocko
2019-10-15 14:23 ` Oscar Salvador
2019-10-10 0:26 ` Naoya Horiguchi
2019-10-10 7:17 ` David Hildenbrand
2019-10-11 6:50 ` Naoya Horiguchi
2019-10-19 2:05 ` Andrew Morton
2019-10-21 9:44 ` David Hildenbrand
2019-10-14 8:41 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191009142435.3975-1-david@redhat.com \
--to=david@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anthony.yznaga@oracle.com \
--cc=cai@lca.pw \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pagupta@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=t-fukasawa@vx.jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).