Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp1594863ybv; Thu, 6 Feb 2020 06:40:06 -0800 (PST) X-Google-Smtp-Source: APXvYqwT3QdvV0cZNtAJ03daEag7QtVIE3PSq16j3jBe3x7bot9VYCdgEOqxUJZSJvTn7yIxGIXe X-Received: by 2002:a9d:6497:: with SMTP id g23mr3014532otl.319.1581000006293; Thu, 06 Feb 2020 06:40:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581000006; cv=none; d=google.com; s=arc-20160816; b=z5JTqQoyirMnZsZZrZldYQvu5b2a07Q1Ck8PzA2O6xPkshnWd496U4foInGQAUYgXO t/XW9WjpSQS3oK3SNsqQYfohmlDAvacF/tQ/2xFO8P0UBa0bvAyJURfwQVBmz5j/NEsN rrvHupiOP52dC16so/4jMkbd3K7Tj/CUdRXFNHWZqGkwMENFRImg+tvS42Eiee1iW04c 2CgIx86AwWiKuU2/Ca2v/Pm9AIPOXBdXNNde0MG/NKBbtpZq4nWPr4uEGlUrFyZiC8fe BCQivYI1W8uKkOj6USelWgdKcHXRElk7Hg7lzwVQ4WpRX74JiYFJU/xjUhc7XxxdI2Ig Q+Bg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:autocrypt:from:references:cc:to:subject :dkim-signature; bh=jt/Ln3XG2Jev0ldg1vilWXhlAw1anNmuapIobOSHuKI=; b=xL9B68JVo+b3q8Db0RW08oAZE227zwwYfG6SyxVZ+HV69v3ym7iyOlX1UrTjMu4Qky 8ohuNQRKkaFawZDfKQ+h31wUj2zrbUEQSLGa3LEsQLS32imyH2gsI9RyNy74MVvmkZWz 9ZDEDTAd1ravg4uTdGT8Y8y6XsLjQj6b66w/cmjeYa2OSmm8JlmbphrYVHlZ037i2dHP 4/IrIF3UY4sSkV5/KuVkL/Iuhla9VUpGtYjBPGV4zHSyAemz3Dz5XLxsQMWCYL6U/P02 pCUC+Bn+jkk+13AUX10gox6XkrPCIEKhBnXR6oSZU4H2wpKYpw6K0PK+TFHRT5SLkgG2 5dcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eNUpl1y2; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64si1989687otx.50.2020.02.06.06.39.53; Thu, 06 Feb 2020 06:40:06 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eNUpl1y2; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728016AbgBFOhu (ORCPT + 99 others); Thu, 6 Feb 2020 09:37:50 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:22178 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727872AbgBFOhu (ORCPT ); Thu, 6 Feb 2020 09:37:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580999869; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=jt/Ln3XG2Jev0ldg1vilWXhlAw1anNmuapIobOSHuKI=; b=eNUpl1y25HEZWy3WOIJYmwf8GSW7zJ/eEx3n5du3x6/yjX0K3HMo9l+TZWMg00CmAc2gGj NFPOGRfqF9oq9RaqtKtqCyrOMrdeT2vmbmBhAsCNLBj/GKYDjIItHbmRBR/mdmZHQveWM4 wLoF721FNbmtvB2vLDXVqlQOoFjTIbE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-299-ZR9i1TwBNkyYRKkLT3fC0g-1; Thu, 06 Feb 2020 09:37:45 -0500 X-MC-Unique: ZR9i1TwBNkyYRKkLT3fC0g-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0BCED106BCBA; Thu, 6 Feb 2020 14:37:43 +0000 (UTC) Received: from [10.36.118.128] (unknown [10.36.118.128]) by smtp.corp.redhat.com (Postfix) with ESMTP id 488FD48; Thu, 6 Feb 2020 14:37:41 +0000 (UTC) Subject: Re: [PATCH] mm/sparsemem: pfn_to_page is not valid yet on SPARSEMEM To: Baoquan He Cc: Wei Yang , akpm@linux-foundation.org, osalvador@suse.de, dan.j.williams@intel.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20200206125343.9070-1-richardw.yang@linux.intel.com> <6d9e36cb-ee4a-00c8-447b-9b75a0262c3a@redhat.com> <20200206135016.GA25537@MiWiFi-R3L-srv> <87bb4563-481d-cce9-b916-50a098558210@redhat.com> <20200206140703.GB25537@MiWiFi-R3L-srv> From: David Hildenbrand Autocrypt: addr=david@redhat.com; prefer-encrypt=mutual; keydata= mQINBFXLn5EBEAC+zYvAFJxCBY9Tr1xZgcESmxVNI/0ffzE/ZQOiHJl6mGkmA1R7/uUpiCjJ dBrn+lhhOYjjNefFQou6478faXE6o2AhmebqT4KiQoUQFV4R7y1KMEKoSyy8hQaK1umALTdL QZLQMzNE74ap+GDK0wnacPQFpcG1AE9RMq3aeErY5tujekBS32jfC/7AnH7I0v1v1TbbK3Gp XNeiN4QroO+5qaSr0ID2sz5jtBLRb15RMre27E1ImpaIv2Jw8NJgW0k/D1RyKCwaTsgRdwuK Kx/Y91XuSBdz0uOyU/S8kM1+ag0wvsGlpBVxRR/xw/E8M7TEwuCZQArqqTCmkG6HGcXFT0V9 PXFNNgV5jXMQRwU0O/ztJIQqsE5LsUomE//bLwzj9IVsaQpKDqW6TAPjcdBDPLHvriq7kGjt WhVhdl0qEYB8lkBEU7V2Yb+SYhmhpDrti9Fq1EsmhiHSkxJcGREoMK/63r9WLZYI3+4W2rAc UucZa4OT27U5ZISjNg3Ev0rxU5UH2/pT4wJCfxwocmqaRr6UYmrtZmND89X0KigoFD/XSeVv jwBRNjPAubK9/k5NoRrYqztM9W6sJqrH8+UWZ1Idd/DdmogJh0gNC0+N42Za9yBRURfIdKSb B3JfpUqcWwE7vUaYrHG1nw54pLUoPG6sAA7Mehl3nd4pZUALHwARAQABtCREYXZpZCBIaWxk ZW5icmFuZCA8ZGF2aWRAcmVkaGF0LmNvbT6JAlgEEwEIAEICGwMFCQlmAYAGCwkIBwMCBhUI AgkKCwQWAgMBAh4BAheAFiEEG9nKrXNcTDpGDfzKTd4Q9wD/g1oFAl3pImkCGQEACgkQTd4Q 9wD/g1o+VA//SFvIHUAvul05u6wKv/pIR6aICPdpF9EIgEU448g+7FfDgQwcEny1pbEzAmiw zAXIQ9H0NZh96lcq+yDLtONnXk/bEYWHHUA014A1wqcYNRY8RvY1+eVHb0uu0KYQoXkzvu+s Dncuguk470XPnscL27hs8PgOP6QjG4jt75K2LfZ0eAqTOUCZTJxA8A7E9+XTYuU0hs7QVrWJ jQdFxQbRMrYz7uP8KmTK9/Cnvqehgl4EzyRaZppshruKMeyheBgvgJd5On1wWq4ZUV5PFM4x II3QbD3EJfWbaJMR55jI9dMFa+vK7MFz3rhWOkEx/QR959lfdRSTXdxs8V3zDvChcmRVGN8U Vo93d1YNtWnA9w6oCW1dnDZ4kgQZZSBIjp6iHcA08apzh7DPi08jL7M9UQByeYGr8KuR4i6e RZI6xhlZerUScVzn35ONwOC91VdYiQgjemiVLq1WDDZ3B7DIzUZ4RQTOaIWdtXBWb8zWakt/ ztGhsx0e39Gvt3391O1PgcA7ilhvqrBPemJrlb9xSPPRbaNAW39P8ws/UJnzSJqnHMVxbRZC Am4add/SM+OCP0w3xYss1jy9T+XdZa0lhUvJfLy7tNcjVG/sxkBXOaSC24MFPuwnoC9WvCVQ ZBxouph3kqc4Dt5X1EeXVLeba+466P1fe1rC8MbcwDkoUo65Ag0EVcufkQEQAOfX3n0g0fZz Bgm/S2zF/kxQKCEKP8ID+Vz8sy2GpDvveBq4H2Y34XWsT1zLJdvqPI4af4ZSMxuerWjXbVWb T6d4odQIG0fKx4F8NccDqbgHeZRNajXeeJ3R7gAzvWvQNLz4piHrO/B4tf8svmRBL0ZB5P5A 2uhdwLU3NZuK22zpNn4is87BPWF8HhY0L5fafgDMOqnf4guJVJPYNPhUFzXUbPqOKOkL8ojk CXxkOFHAbjstSK5Ca3fKquY3rdX3DNo+EL7FvAiw1mUtS+5GeYE+RMnDCsVFm/C7kY8c2d0G NWkB9pJM5+mnIoFNxy7YBcldYATVeOHoY4LyaUWNnAvFYWp08dHWfZo9WCiJMuTfgtH9tc75 7QanMVdPt6fDK8UUXIBLQ2TWr/sQKE9xtFuEmoQGlE1l6bGaDnnMLcYu+Asp3kDT0w4zYGsx 5r6XQVRH4+5N6eHZiaeYtFOujp5n+pjBaQK7wUUjDilPQ5QMzIuCL4YjVoylWiBNknvQWBXS lQCWmavOT9sttGQXdPCC5ynI+1ymZC1ORZKANLnRAb0NH/UCzcsstw2TAkFnMEbo9Zu9w7Kv AxBQXWeXhJI9XQssfrf4Gusdqx8nPEpfOqCtbbwJMATbHyqLt7/oz/5deGuwxgb65pWIzufa N7eop7uh+6bezi+rugUI+w6DABEBAAGJAiUEGAECAA8FAlXLn5ECGwwFCQlmAYAACgkQTd4Q 9wD/g1qA6w/+M+ggFv+JdVsz5+ZIc6MSyGUozASX+bmIuPeIecc9UsFRatc91LuJCKMkD9Uv GOcWSeFpLrSGRQ1Z7EMzFVU//qVs6uzhsNk0RYMyS0B6oloW3FpyQ+zOVylFWQCzoyyf227y GW8HnXunJSC+4PtlL2AY4yZjAVAPLK2l6mhgClVXTQ/S7cBoTQKP+jvVJOoYkpnFxWE9pn4t H5QIFk7Ip8TKr5k3fXVWk4lnUi9MTF/5L/mWqdyIO1s7cjharQCstfWCzWrVeVctpVoDfJWp 4LwTuQ5yEM2KcPeElLg5fR7WB2zH97oI6/Ko2DlovmfQqXh9xWozQt0iGy5tWzh6I0JrlcxJ ileZWLccC4XKD1037Hy2FLAjzfoWgwBLA6ULu0exOOdIa58H4PsXtkFPrUF980EEibUp0zFz GotRVekFAceUaRvAj7dh76cToeZkfsjAvBVb4COXuhgX6N4pofgNkW2AtgYu1nUsPAo+NftU CxrhjHtLn4QEBpkbErnXQyMjHpIatlYGutVMS91XTQXYydCh5crMPs7hYVsvnmGHIaB9ZMfB njnuI31KBiLUks+paRkHQlFcgS2N3gkRBzH7xSZ+t7Re3jvXdXEzKBbQ+dC3lpJB0wPnyMcX FOTT3aZT7IgePkt5iC/BKBk3hqKteTnJFeVIT7EC+a6YUFg= Organization: Red Hat GmbH Message-ID: Date: Thu, 6 Feb 2020 15:37:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <20200206140703.GB25537@MiWiFi-R3L-srv> Content-Type: text/plain; charset=utf-8 Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06.02.20 15:07, Baoquan He wrote: > On 02/06/20 at 02:55pm, David Hildenbrand wrote: >> On 06.02.20 14:50, Baoquan He wrote: >>> On 02/06/20 at 02:28pm, David Hildenbrand wrote: >>>> On 06.02.20 13:53, Wei Yang wrote: >>>>> When we use SPARSEMEM instead of SPARSEMEM_VMEMMAP, pfn_to_page() >>>>> doesn't work before sparse_init_one_section() is called. This leads= to a >>>>> crash when hotplug memory. >>>>> >>>>> We should use memmap as it did. >>>>> >>>>> Fixes: ba72b4c8cf60 ("mm/sparsemem: support sub-section hotplug") >>>>> Signed-off-by: Wei Yang >>>>> CC: Dan Williams >>>>> --- >>>>> mm/sparse.c | 2 +- >>>>> 1 file changed, 1 insertion(+), 1 deletion(-) >>>>> >>>>> diff --git a/mm/sparse.c b/mm/sparse.c >>>>> index 5a8599041a2a..2efb24ff8f96 100644 >>>>> --- a/mm/sparse.c >>>>> +++ b/mm/sparse.c >>>>> @@ -882,7 +882,7 @@ int __meminit sparse_add_section(int nid, unsig= ned long start_pfn, >>>>> * Poison uninitialized struct pages in order to catch invalid fl= ags >>>>> * combinations. >>>>> */ >>>>> - page_init_poison(pfn_to_page(start_pfn), sizeof(struct page) * nr= _pages); >>>>> + page_init_poison(memmap, sizeof(struct page) * nr_pages); >>>> >>>> If you add sub-sections that don't fall onto the start of the sectio= n, >>>> >>>> pfn_to_page(start_pfn) !=3D memmap >>>> >>>> and your patch would break that under SPARSEMEM_VMEMMAP if I am not = wrong. >>> >>> It returns the pfn_to_page(pfn) from __populate_section_memmap() and >>> assign to memmap in vmemmap case, how come it breaks anything. Correc= t >>> me if I was wrong. >> >> I'm sorry, I can't follow :) Can you elaborate? >> >> Was your comment targeted at why the old code cannot be broken or why >> this patch cannot be broken? >=20 > Sorry for the confusion :-) the latter. I mean the returned memmap has = been > at the pfn_to_page(start_pfn) in SPARSEMEM_VMEMMAP case. Yeah, at least for SPARSEMEM_VMEMMAP it is indeed right. Thanks :) Now, about SPARSEMEM: populate_section_memmap() does not care about nr_pages and will allocate a memmap for the whole section. So, whenever we add sub-sections to a section, we allocate a new memmap for the whole section. And we do overwrite the memmap pointer in our section. ( sparse_add_section() ) That makes me assume that sub-section hot-add under SPARSEMEM is either a) never enabled and only works with SPARSEMEM_VMEMMAP b) horribly broken And I think a) applies (looking at pfn_section_valid()). Therefore, we don't have to care about sub-section hot-add specifics (and I would be broken already) Acked-by: David Hildenbrand --=20 Thanks, David / dhildenb