From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) by kanga.kvack.org (Postfix) with ESMTP id E91E26B027E for ; Tue, 24 Jul 2018 05:50:21 -0400 (EDT) Received: by mail-ed1-f70.google.com with SMTP id g5-v6so1535372edp.1 for ; Tue, 24 Jul 2018 02:50:21 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id c9-v6si1101736edn.411.2018.07.24.02.50.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Jul 2018 02:50:20 -0700 (PDT) Subject: Re: [PATCH v1 0/2] mm/kdump: exclude reserved pages in dumps References: <20180720123422.10127-1-david@redhat.com> <9f46f0ed-e34c-73be-60ca-c892fb19ed08@suse.cz> <20180724072237.GA28386@dhcp22.suse.cz> From: Vlastimil Babka Message-ID: Date: Tue, 24 Jul 2018 11:48:00 +0200 MIME-Version: 1.0 In-Reply-To: <20180724072237.GA28386@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko , David Hildenbrand Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Baoquan He , Dave Young , Greg Kroah-Hartman , Hari Bathini , Huang Ying , "Kirill A. Shutemov" , =?UTF-8?Q?Marc-Andr=c3=a9_Lureau?= , Matthew Wilcox , Miles Chen , Pavel Tatashin , Petr Tesarik On 07/24/2018 09:22 AM, Michal Hocko wrote: > On Mon 23-07-18 19:12:58, David Hildenbrand wrote: >> 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? > > But we do not have many page flags spare and even if we have one or two > this doesn't look like the use for them. So I still think we should try > the PageReserved way. First we would have to audit everything that's using PageReserved and might be important for the crash dump to be useful. memmap might not be the only case...