From: David Hildenbrand <david@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
"David Hildenbrand" <david@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Baoquan He" <bhe@redhat.com>, "Dave Young" <dyoung@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Hari Bathini" <hbathini@linux.vnet.ibm.com>,
"Huang Ying" <ying.huang@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Matthew Wilcox" <mawilcox@microsoft.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Michal Hocko" <mhocko@suse.com>,
"Miles Chen" <miles.chen@mediatek.com>,
"Pavel Tatashin" <pasha.tatashin@oracle.com>,
"Petr Tesarik" <ptesarik@suse.cz>,
"Vlastimil Babka" <vbabka@suse.cz>
Subject: [PATCH v1 0/2] mm/kdump: exclude reserved pages in dumps
Date: Fri, 20 Jul 2018 14:34:20 +0200 [thread overview]
Message-ID: <20180720123422.10127-1-david@redhat.com> (raw)
Dumping tools (like makedumpfile) right now don't exclude reserved pages.
So reserved pages might be access by dump tools although nobody except
the owner should touch them.
This is relevant in virtual environments where we soon might want to
report certain reserved pages to the hypervisor and they might no longer
be accessible - what already was documented for reserved pages a long
time ago ("might not even exist").
David Hildenbrand (2):
mm: clarify semantics of reserved pages
kdump: include PG_reserved value in VMCOREINFO
include/linux/page-flags.h | 4 ++--
kernel/crash_core.c | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-20 12:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 12:34 David Hildenbrand [this message]
2018-07-20 12:34 ` [PATCH v1 1/2] mm: clarify semantics of reserved pages David Hildenbrand
2018-07-20 12:34 ` David Hildenbrand
2018-07-23 10:48 ` Michal Hocko
2018-07-23 10:48 ` Michal Hocko
2018-07-20 12:34 ` [PATCH v1 2/2] kdump: include PG_reserved value in VMCOREINFO David Hildenbrand
2018-07-23 11:45 ` [PATCH v1 0/2] mm/kdump: exclude reserved pages in dumps Vlastimil Babka
2018-07-23 12:30 ` Michal Hocko
2018-07-23 17:20 ` David Hildenbrand
2018-07-24 7:25 ` Michal Hocko
2018-07-24 8:46 ` David Hildenbrand
2018-07-24 8:53 ` Michal Hocko
2018-07-24 9:18 ` David Hildenbrand
2018-07-24 12:17 ` David Hildenbrand
2018-07-24 13:13 ` Michal Hocko
2018-07-24 13:27 ` David Hildenbrand
2018-07-24 13:35 ` Michal Hocko
2018-07-24 14:13 ` David Hildenbrand
2018-07-25 13:51 ` Michal Hocko
2018-07-25 14:20 ` David Hildenbrand
2018-07-26 8:27 ` Michal Hocko
2018-07-26 8:37 ` David Hildenbrand
2018-07-24 9:47 ` Vlastimil Babka
2018-07-24 11:19 ` Michal Hocko
2018-07-24 12:22 ` Vlastimil Babka
2018-07-24 12:33 ` David Hildenbrand
2018-07-24 13:06 ` Michal Hocko
2018-07-23 17:12 ` David Hildenbrand
2018-07-24 7:22 ` Michal Hocko
2018-07-24 9:48 ` Vlastimil Babka
2018-07-26 8:22 ` David Hildenbrand
2018-07-26 8:30 ` Michal Hocko
2018-07-26 8:45 ` David Hildenbrand
2018-07-26 19:50 ` Andrew Morton
2018-07-30 8:17 ` 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=20180720123422.10127-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcandre.lureau@redhat.com \
--cc=mawilcox@microsoft.com \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=miles.chen@mediatek.com \
--cc=pasha.tatashin@oracle.com \
--cc=ptesarik@suse.cz \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.