On 23.07.2018 13:45, Vlastimil Babka wrote:
> On 07/20/2018 02:34 PM, David Hildenbrand wrote:
>> 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.
>
> Are you sure about that? Or maybe I understand wrong. Maybe it changed
> recently, but IIRC pages that are backing memmap (struct pages) are also
> PG_reserved. And you definitely do want those in the dump.
I proposed a new flag/value to mask pages that are logically offline but
Michal wanted me to go into this direction.
While we can special case struct pages in dump tools ("we have to
read/interpret them either way, so we can also dump them"), it smells
like my original attempt was cleaner. Michal?
>
>> 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(-)
>>
>
--
Thanks,
David / dhildenb
