Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp14410458pxu; Tue, 5 Jan 2021 00:20:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJy2BTnH/UbgeVf4qQ+jLU99JJS8zuxzsICWhQDAjiVLD+UFc6zXI06p8v9FbEEdTV1nLwuC X-Received: by 2002:a17:906:6b88:: with SMTP id l8mr69608546ejr.482.1609834801944; Tue, 05 Jan 2021 00:20:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609834801; cv=none; d=google.com; s=arc-20160816; b=tNcADmsV85i1rAtiXRmPXQRHPSiVcDg2Inbn64sZUaiKBhK1WcvYYzAPDU87XJTbYv FP4pxMPxu2IaJ/qqn5SgshZhFqNXQNzYl6wCT3LZlLDeQlqY9xxCIOLLsXAHfAsKWxao Q3VfVBAo5fa5+NoN/BB2Rrdg3vciEtFoUz70nfOx4yn9kwbjnd+XWgw8muL0BqUp8thv MyS9Ku9bn5J8P4c106OU8wEe/bJ9AwyIPU0Ao4vcJnzvPSSvqBZ3Gs+MgA+jXJRYfvRW lYop8p3kJUoYDd40KM4GFNAtwk/XUtpMfIbUGZPCuYbM7stBa/3fjfrJI6iR/rfhAjw2 0MBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=zYLn+vdZQ/DSl04YjE7uuZY8XIpP1A4GnWwXJuDBAco=; b=Ax6TzwI/C65mGvOsKM47wnYrtAh70NHE8Usd4YSZCLxi/ImhDOSmkNaKfk26gZh53D N6Ehh3zrEM2GKk5gV2sdfegflX7NxHoF48bkzVR7xxRFQwEmRQjYF3aBetzNJYPTPkuZ wIwTotMv/Fkco6joVmLYk+uS6iztjTnMTiB5Ka0lxTuseG/93djKW8N6djNesZB7Rft0 KElyDDhRgGxtTEwTV4vK4Zqwnyw6924hOn6PgqasRS3t3OWlAfZOFALkOstxPVqQjxQW PViRolEsdTqbZYeC3w6WWTr1tHu4RQx77QIxDSjtLGLaYNa4JFKvmxx6oBY8fhNpvzgb CfoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=cS8ev0d5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a3si32416788edt.452.2021.01.05.00.19.38; Tue, 05 Jan 2021 00:20:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=cS8ev0d5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727063AbhAEIRm (ORCPT + 99 others); Tue, 5 Jan 2021 03:17:42 -0500 Received: from mx2.suse.de ([195.135.220.15]:57988 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725535AbhAEIRm (ORCPT ); Tue, 5 Jan 2021 03:17:42 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1609834615; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zYLn+vdZQ/DSl04YjE7uuZY8XIpP1A4GnWwXJuDBAco=; b=cS8ev0d5S4LK7OsiiKLIWIoPz+jWMmhboAYLDPrCcXZS9NCBLHNjk/noR+dRBHtkC0wC6p zcbOjwgXTLKHf0OtaN3kNnsrPaUlXe8HTIex62mnE8HK2NbQymUFTUNqyGc7xsy4GKU6dT qv0qkuJOcz/jHhhcZSFs7UOzlRkp6Yw= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 502FDAA35; Tue, 5 Jan 2021 08:16:55 +0000 (UTC) Date: Tue, 5 Jan 2021 09:16:54 +0100 From: Michal Hocko To: David Hildenbrand Cc: Dan Williams , linux-mm@kvack.org, LKML , Oscar Salvador Subject: Re: uninitialized pmem struct pages Message-ID: <20210105081654.GU13207@dhcp22.suse.cz> References: <20210104100323.GC13207@dhcp22.suse.cz> <033e1cd6-9762-5de6-3e88-47d3038fda7f@redhat.com> <20210104142624.GI13207@dhcp22.suse.cz> <23a4eea2-9fdb-fd1d-ee92-9cd8ac6e8f41@redhat.com> <20210104151005.GK13207@dhcp22.suse.cz> <26db2c3e-10c7-c6e3-23f7-21eb5101b31a@redhat.com> <20210104153300.GL13207@dhcp22.suse.cz> <6106ca7f-3247-0916-3e1e-ad6af17272ea@redhat.com> <20210105080057.GT13207@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210105080057.GT13207@dhcp22.suse.cz> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 05-01-21 09:01:00, Michal Hocko wrote: > On Mon 04-01-21 16:44:52, David Hildenbrand wrote: > > On 04.01.21 16:43, David Hildenbrand wrote: > > > On 04.01.21 16:33, Michal Hocko wrote: > > >> On Mon 04-01-21 16:15:23, David Hildenbrand wrote: > > >>> On 04.01.21 16:10, Michal Hocko wrote: > > >> [...] > > >>> Do the physical addresses you see fall into the same section as boot > > >>> memory? Or what's around these addresses? > > >> > > >> Yes I am getting a garbage for the first struct page belonging to the > > >> pmem section [1] > > >> [ 0.020161] ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0x603fffffff] > > >> [ 0.020163] ACPI: SRAT: Node 4 PXM 4 [mem 0x6060000000-0x11d5fffffff] non-volatile > > >> > > >> The pfn without the initialized struct page is 0x6060000. This is a > > >> first pfn in a section. > > > > > > Okay, so we're not dealing with the "early section" mess I described, > > > different story. > > > > > > Due to [1], is_mem_section_removable() called > > > pfn_to_page(PHYS_PFN(0x6060000)). page_zone(page) made it crash, as not > > > initialized. > > > > > > Let's assume this is indeed a reserved pfn in the altmap. What's the > > > actual address of the memmap? > > > > > > I do wonder what hosts pfn_to_page(PHYS_PFN(0x6060000)) - is it actually > > > part of the actual altmap (i.e. > 0x6060000) or maybe even self-hosted? > > > > > > If it's not self-hosted, initializing the relevant memmaps should work > > > just fine I guess. Otherwise things get more complicated. > > > > Oh, I forgot: pfn_to_online_page() should at least in your example make > > sure other pfn walkers are safe. It was just an issue of > > is_mem_section_removable(). > > Hmm, I suspect you are right. I haven't put this together, thanks! The memory > section is indeed marked offline so pfn_to_online_page would indeed bail > out: > crash> p (0x6060000>>15) > $3 = 3084 > crash> p mem_section[3084/128][3084 & 127] > $4 = { > section_mem_map = 18446736128020054019, > usage = 0xffff902dcf956680, > page_ext = 0x0, > pad = 0 > } > crash> p 18446736128020054019 & (1UL<<2) > $5 = 0 > > That makes it considerably less of a problem than I thought! Forgot to add that those who are running kernels without 53cdc1cb29e8 ("drivers/base/memory.c: indicate all memory blocks as removable") for some reason can fix the crash by the following simple patch. Index: linux-5.3-users_mhocko_SLE15-SP2_for-next/drivers/base/memory.c =================================================================== --- linux-5.3-users_mhocko_SLE15-SP2_for-next.orig/drivers/base/memory.c +++ linux-5.3-users_mhocko_SLE15-SP2_for-next/drivers/base/memory.c @@ -152,9 +152,14 @@ static ssize_t removable_show(struct dev goto out; for (i = 0; i < sections_per_block; i++) { - if (!present_section_nr(mem->start_section_nr + i)) + unsigned long nr = mem->start_section_nr + i; + if (!present_section_nr(nr)) continue; - pfn = section_nr_to_pfn(mem->start_section_nr + i); + if (!online_section_nr()) { + ret = 0; + break; + } + pfn = section_nr_to_pfn(nr); ret &= is_mem_section_removable(pfn, PAGES_PER_SECTION); } -- Michal Hocko SUSE Labs