Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp4640406pxu; Thu, 10 Dec 2020 01:30:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJyrr7FbBKb/lzRe4qsP1xv6MiIoLxMcKXOGLJFpxIA3sOfJoofB3Dqv+v+b2MJTa/y/l+yT X-Received: by 2002:a17:906:3899:: with SMTP id q25mr5506185ejd.173.1607592650125; Thu, 10 Dec 2020 01:30:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607592650; cv=none; d=google.com; s=arc-20160816; b=BYpOqCT2lgsBa5aYeGNF6jPoFeDCYpCDzwyPIAduhQ1FIxrYLouj93pTrc9tjuifiz WBRHHbA+LA18Nmp8u05CO4ZJJZ1ge1zIZRAbRMt0hJEEZujfkFEZdx3WS5iY0pmiTyya G9BDMVfTOWQBsrSGNqyVZV0ycRbxAfALt10R5XP4tPlMKiW5WJxto+Yy0kb4z8BuF/BH FojbQgHw0JaLHFfaBNGk7OXsrzezrDEqrhPAxfYeumCkPGaGXtoFY0OV8pCRFPJNO7PT zQsS3tcWUDseQe95mlBFqI/sjmyXVpMTpMud+UiXQc3f/Rjn8KtwVG+BGnwZ34WkjoTD +Utw== 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:dkim-signature:date; bh=hSJA/SAB5GPIaan467DqCMUu2r7caiQ9T34eGFae+/A=; b=V6NzlmoZ3rbM8VaTWWN/Zf80gfloYcgcx/YslahH5GM9hQUTjMfDSFJmHwZ+0GoxQA ezEY+gQXplZDylvq4M38HebDBOmQCxi8+Ismwvyb795IgmEwhXnrKH7jDBZj+u+DIkpn FskVXoQctVV90rmKkuz1BeZ3gqH7qrAcNESEKSQJr2Zn46PywFAZ6GW+GR+5kVG8VUQ+ IwAGoScIZ3fbBg3WlmW5aiBS05WLi1q+KqB5q6/noDBEQWT/N+OamfASwTJjezOVjd6L moB9e6XgJP0RVoQ5W2v4UnxRqr2b9a6qXNHUu/F7+2DDvrakUb3l0QUjr4PADsPBT7RH ngOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=qY5DJbue; 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=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c35si2327757edf.522.2020.12.10.01.30.27; Thu, 10 Dec 2020 01:30:50 -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=@linuxfoundation.org header.s=korg header.b=qY5DJbue; 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=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732055AbgLJJ2i (ORCPT + 99 others); Thu, 10 Dec 2020 04:28:38 -0500 Received: from mail.kernel.org ([198.145.29.99]:38984 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726763AbgLJJ2f (ORCPT ); Thu, 10 Dec 2020 04:28:35 -0500 Date: Thu, 10 Dec 2020 10:29:09 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1607592474; bh=9IBGE7YExpBUElirt6uWH7rWMH+57P9GaY6SS3rQU1k=; h=From:To:Cc:Subject:References:In-Reply-To:From; b=qY5DJbue3kOO4ieeWJO79wbG8Pr/Dlgx50r4S6Ki7OrXc/Drj0uHpOZfs1OEPsQjP XVmgGZlyqPEnL1zxrDXgmYAvHsvC6VdJLofAa3tNB40G+FOlQTA8/k7r3o915Wr0FQ Cw+5C1Jqhi5eFc4Tns+qeTWz0p0yS9AphA3iZiEM= From: Greg KH To: Mike Rapoport Cc: Andrew Morton , Andrea Arcangeli , Baoquan He , David Hildenbrand , Mel Gorman , Michal Hocko , Mike Rapoport , Qian Cai , Vlastimil Babka , linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@vger.kernel.org Subject: Re: [PATCH v2 2/2] mm: fix initialization of struct page for holes in memory layout Message-ID: References: <20201209214304.6812-1-rppt@kernel.org> <20201209214304.6812-3-rppt@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201209214304.6812-3-rppt@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 09, 2020 at 11:43:04PM +0200, Mike Rapoport wrote: > From: Mike Rapoport > > There could be struct pages that are not backed by actual physical memory. > This can happen when the actual memory bank is not a multiple of > SECTION_SIZE or when an architecture does not register memory holes > reserved by the firmware as memblock.memory. > > Such pages are currently initialized using init_unavailable_mem() function > that iterated through PFNs in holes in memblock.memory and if there is a > struct page corresponding to a PFN, the fields if this page are set to > default values and it is marked as Reserved. > > init_unavailable_mem() does not take into account zone and node the page > belongs to and sets both zone and node links in struct page to zero. > > On a system that has firmware reserved holes in a zone above ZONE_DMA, for > instance in a configuration below: > > # grep -A1 E820 /proc/iomem > 7a17b000-7a216fff : Unknown E820 type > 7a217000-7bffffff : System RAM > > unset zone link in struct page will trigger > > VM_BUG_ON_PAGE(!zone_spans_pfn(page_zone(page), pfn), page); > > because there are pages in both ZONE_DMA32 and ZONE_DMA (unset zone link in > struct page) in the same pageblock. > > Interleave initialization of pages that correspond to holes with the > initialization of memory map, so that zone and node information will be > properly set on such pages. > > Fixes: 73a6e474cb37 ("mm: memmap_init: iterate over memblock regions rather > that check each PFN") > Reported-by: Andrea Arcangeli > Signed-off-by: Mike Rapoport > --- > mm/page_alloc.c | 152 +++++++++++++++++++++--------------------------- > 1 file changed, 65 insertions(+), 87 deletions(-) This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly.