Received: by 10.192.165.148 with SMTP id m20csp2508991imm; Thu, 26 Apr 2018 12:12:39 -0700 (PDT) X-Google-Smtp-Source: AIpwx49btdjhGvkbp/81Ta+8TG4OP2eRzGdo8wVaDFgkAOYtA3M4DKjVtStxq1Me1fSyJIrseloE X-Received: by 10.101.81.65 with SMTP id g1mr29249974pgq.104.1524769958960; Thu, 26 Apr 2018 12:12:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524769958; cv=none; d=google.com; s=arc-20160816; b=SDZVcD+vyxuYmHdu6ZEUXmYE30qZUvRB6fBu2EVfRwdHmL80FQRSePYSRCJXT9/vwm RVCFu2xgxxA/TxfW+pyodQUj8VXHVZbM5rCazUsSJ8Fegze9UqP1ZVPLZ6BGSMlecxbp xU6ZZJ3q7ubYcRCzsR8tfdarey7lf6h1575aEw5FrsKfNMqoNlIEJDE8HEh/TrgoLJ9T IAm2b0mN3nN1joKHzyJCLAB6Oe2jDyemJglX1ypu6CzLNMapCSaQ7TGJNhjvZyDx2HPH tC+vmh9pRTqaEX2EyIZZNkEwQTywAyNPRqbfB7uJfpe5NAzDxL0bTBGHQPZGeV+L2nfN 7IGw== 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:arc-authentication-results; bh=PuETjhPODeWnVNeZhl9gbBGM1ByNXaC//yCrGKlDSnI=; b=VT6TqtGyzD1NDufNh+6jO7bkU9bIhqY70gUrALDubQOLW0iG7XnwxFZH2hg6yVN00U KC2f6bPM+Y3zf1SJYObXVzOFrW1ONalXIId40bEc/NLZMEed9/y3lGushUqUr1P1lvnQ w4wxdp/3ErXKLMdBA5lbOe++vep0Ez/4HARTO0mCFTE1wZmoz/p3Jk3Z06xRLtQXEX3o 66KWdI/mbjtgUs986ued0WTsPOVLBovDBKzk4Ds6ubdIVf3H027myRIcWPRJdxS8tLeI TXzevm6QBWroel4NAngUAJjju1oXvRd1tT1Ke5tqUSPmD4HGDWFrz6ONWHzlblXmFUGZ k3ng== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c23-v6si19806644plk.245.2018.04.26.12.12.24; Thu, 26 Apr 2018 12:12:38 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753603AbeDZTLQ (ORCPT + 99 others); Thu, 26 Apr 2018 15:11:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:37818 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751645AbeDZTLP (ORCPT ); Thu, 26 Apr 2018 15:11:15 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id BC100AD7F; Thu, 26 Apr 2018 19:11:13 +0000 (UTC) Date: Thu, 26 Apr 2018 21:11:11 +0200 From: Michal Hocko To: Pavel Tatashin Cc: steven.sistare@oracle.com, daniel.m.jordan@oracle.com, akpm@linux-foundation.org, kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH] mm: sections are not offlined during memory hotremove Message-ID: <20180426191111.GV17484@dhcp22.suse.cz> References: <20180426155834.16845-1-pasha.tatashin@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180426155834.16845-1-pasha.tatashin@oracle.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 26-04-18 11:58:34, Pavel Tatashin wrote: > Memory hotplug, and hotremove operate with per-block granularity. If > machine has large amount of memory (more than 64G), the size of memory > block can span multiple sections. By mistake, during hotremove we set > only the first section to offline state. > > The bug was discovered because kernel selftest started to fail: > https://lkml.kernel.org/r/20180423011247.GK5563@yexl-desktop > > After commit, "mm/memory_hotplug: optimize probe routine". But, the bug is > older than this commit. In this optimization we also added a check for > sections to be in a proper state during hotplug operation. > > Fixes: 2d070eab2e82 ("mm: consider zone which is not fully populated to have holes") Dohh. When I saw this I've had that feeling that I have fixed this already and it must have get lost somewhere. But no, this was the same bug in a different path b4ccec41af82 ("mm/sparse.c: fix typo in online_mem_sections"). I wonder why I haven't noticed the same pattern in the offline path. Thanks for noticing and fixing this. > Signed-off-by: Pavel Tatashin Acked-by: Michal Hocko > --- > mm/sparse.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mm/sparse.c b/mm/sparse.c > index 62eef264a7bd..73dc2fcc0eab 100644 > --- a/mm/sparse.c > +++ b/mm/sparse.c > @@ -629,7 +629,7 @@ void offline_mem_sections(unsigned long start_pfn, unsigned long end_pfn) > unsigned long pfn; > > for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) { > - unsigned long section_nr = pfn_to_section_nr(start_pfn); > + unsigned long section_nr = pfn_to_section_nr(pfn); > struct mem_section *ms; > > /* > -- > 1.8.3.1 > -- Michal Hocko SUSE Labs