Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp6947617ybi; Thu, 1 Aug 2019 00:49:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxGvSum+tjOLF6uUGcjPDDysJVz7DLSZxtYbmRO/VcKLq5speH/Wz8cs/31XvEuxVteZWw X-Received: by 2002:a17:90a:3ac2:: with SMTP id b60mr7180056pjc.74.1564645745604; Thu, 01 Aug 2019 00:49:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564645745; cv=none; d=google.com; s=arc-20160816; b=Gpw7cZTIEOnXXuhySqynQ9N3aEJiVbnRrisZ5Uk5WsYhKUPYcaBw0/r3HSzImtlioV Zd6Ho8VJIGbhNygwDLCwKazn7VLHULOUlgKJtm2eNDIq/cnZv4B8TowyL7w5OSJGuFgJ GWLEd8wfUTQnQ3LUGevLGrdeMHA00LKp/Bl17cR+cGKJteFfrVUX/l5HLnSI2xddKK2P /KKrcBGdMYpubinuuRG3WuI2QYmyFOvWMhn1gBTDXVMrU6b6YxLoLZXIj2NgbJhImz8P 4B6yhNt9XSVXqjfm+WQluSnkct7ABD1AmYt7tIWn2Qz/ndaAoG3+8D63vvnQVLLWRNc+ j/Qw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=/jGc3/JCEsP768NrzTx/5aigSMBX+P0d6dquZnS8Vlc=; b=y+nFDeK2FNVGcVyHLlX4unKHDNn1ct7xIGxbiTn8+vj9hXrkrJaPBS1QFUdLvhVNVb 6Fg+z7aFe9Y0+WTD8wDdBGuSzuV2wYVNi+hBbqhdcy1eAvps/ddDh70Vxs6ZRwl/8eWq diTwqYd7CbJQsdo1iccCBBrd+ST+HSp9IF3rbjqQSdfD47kpSMtPp9R9kkPNFOf/04ng n0jv4ZRxLc2/8NfBfJ6X11Qnd3tGGVrbLKQMDB3hzgulR/rbF9v5CboWQDxr65t4BeNX xh6R8hsBhBVxwh5nO6Jh9gAgbDRSi7yWnOCn5sSRRupAHk0wdGMQmZsSwh8lCLgyJpc/ qpiw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l63si35758146pfl.41.2019.08.01.00.48.50; Thu, 01 Aug 2019 00:49:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729447AbfHAHkK (ORCPT + 99 others); Thu, 1 Aug 2019 03:40:10 -0400 Received: from mx2.suse.de ([195.135.220.15]:59984 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725804AbfHAHkK (ORCPT ); Thu, 1 Aug 2019 03:40:10 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 55B34B11C; Thu, 1 Aug 2019 07:40:09 +0000 (UTC) Date: Thu, 1 Aug 2019 09:39:57 +0200 From: Michal Hocko To: David Hildenbrand Cc: Rashmica Gupta , Oscar Salvador , Andrew Morton , Dan Williams , pasha.tatashin@soleen.com, Jonathan.Cameron@huawei.com, anshuman.khandual@arm.com, Vlastimil Babka , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/5] Allocate memmap from hotadded memory Message-ID: <20190801073957.GH11627@dhcp22.suse.cz> References: <9143f64391d11aa0f1988e78be9de7ff56e4b30b.camel@gmail.com> <20190702074806.GA26836@linux> <20190731120859.GJ9330@dhcp22.suse.cz> <4ddee0dd719abd50350f997b8089fa26f6004c0c.camel@gmail.com> <20190801071709.GE11627@dhcp22.suse.cz> <9bcbd574-7e23-5cfe-f633-646a085f935a@redhat.com> <20190801072430.GF11627@dhcp22.suse.cz> <5e6137c9-5269-5756-beaa-d116652be8b9@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e6137c9-5269-5756-beaa-d116652be8b9@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 01-08-19 09:31:09, David Hildenbrand wrote: > On 01.08.19 09:26, David Hildenbrand wrote: [...] > > I am not sure about the implications of having > > pfn_valid()/pfn_present()/pfn_online() return true but accessing it > > results in crashes. (suspend, kdump, whatever other technology touches > > online memory) > > (oneidea: we could of course go ahead and mark the pages PG_offline > before unmapping the pfn range to work around these issues) PG_reserved and an elevated reference count should be enough to drive any pfn walker out. Pfn walkers shouldn't touch any page unless they know and recognize their type. -- Michal Hocko SUSE Labs