Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp1344979ybg; Fri, 18 Oct 2019 16:23:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqx/d8SZ3W089lK5IE+Nhm4mlK9fq9hnQNqf7PBAcV/3i2GKYls289cr8pmAuytc3BBMDlVv X-Received: by 2002:a17:906:4895:: with SMTP id v21mr6734731ejq.2.1571440990033; Fri, 18 Oct 2019 16:23:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571440990; cv=none; d=google.com; s=arc-20160816; b=BydpD7rdR+UxQrOTrGeRvDeHlx14CFYTC3g2F9OZ9+E70JW2c92HN/u0tGX5+tx76F 1XrVysKdT5E94m9ChRa9GsulM3de3x+GfSLzHrpzDrrKsdRIvHLD7dVSsHIuhnMFlS99 +AU45d/i5uGjTFhLkTMaPtZ3HQvSbsuF/XSERHw6XZ48i0gh0riYq/OdhU9mzBlM77wJ yXuosrAwgnLGVsTO0aAf1JwAZnhgxzKDJiui6w+UIAKKnV+qv5jlmSwMhVIVsMw2yaKQ b2QwnGdIstlvpHrp3FBaGVLBLcjn8CqDtfWBUxKj49SF80hhcEuPp36kbji4Me9zFVVu wbnw== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=J/L+xRHdxqa5TQWem2XAMc0Gx4IJDT5ineJ5qW4eYgs=; b=0NSa+8vr5WjEBwewusCUiyMLuKCMOvOAg+KivcN68McJCQofAeC5hSFOVBhBkt7eBq KI4UNHT78PCnerR1EsbouH8EYnjtSWEZvV8T7a9bpcY6Xm57zkaL4HvDfnKv24RmzXGu ceLqN0y1w2+EiFELVJqY6afs/bFzV0++exIMgzE6I2q09ogjWGjw2EwNZVq1OLvmEelz ckpSna3V7XbqrNLJwnxQll2kVgR4Fan/0YcrevE6N2TqAlYfVfMc99dzoZSKFAc8mBBw j7Aa4Xh59pgeGE00ksOsAxhmfxLojkNR1+81ElPDvXwJENWeNKiJSI8+IHEA+BqO9q1p iUlA== 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 fy18si401204ejb.371.2019.10.18.16.22.47; Fri, 18 Oct 2019 16:23:10 -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 S2504274AbfJRGGi (ORCPT + 99 others); Fri, 18 Oct 2019 02:06:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:43010 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1732869AbfJRGGi (ORCPT ); Fri, 18 Oct 2019 02:06:38 -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 72203AC9D; Fri, 18 Oct 2019 06:06:36 +0000 (UTC) Date: Fri, 18 Oct 2019 08:06:35 +0200 From: Michal Hocko To: Naoya Horiguchi Cc: Qian Cai , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , David Hildenbrand , Mike Kravetz Subject: Re: memory offline infinite loop after soft offline Message-ID: <20191018060635.GA5017@dhcp22.suse.cz> References: <1570829564.5937.36.camel@lca.pw> <20191014083914.GA317@dhcp22.suse.cz> <20191017093410.GA19973@hori.linux.bs1.fc.nec.co.jp> <20191017100106.GF24485@dhcp22.suse.cz> <1571335633.5937.69.camel@lca.pw> <20191017182759.GN24485@dhcp22.suse.cz> <20191018021906.GA24978@hori.linux.bs1.fc.nec.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191018021906.GA24978@hori.linux.bs1.fc.nec.co.jp> 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 Fri 18-10-19 02:19:06, Naoya Horiguchi wrote: > On Thu, Oct 17, 2019 at 08:27:59PM +0200, Michal Hocko wrote: > > On Thu 17-10-19 14:07:13, Qian Cai wrote: > > > On Thu, 2019-10-17 at 12:01 +0200, Michal Hocko wrote: > > > > On Thu 17-10-19 09:34:10, Naoya Horiguchi wrote: > > > > > On Mon, Oct 14, 2019 at 10:39:14AM +0200, Michal Hocko wrote: > > > > > > > > [...] > > > > > > diff --git a/mm/page_isolation.c b/mm/page_isolation.c > > > > > > index 89c19c0feadb..5fb3fee16fde 100644 > > > > > > --- a/mm/page_isolation.c > > > > > > +++ b/mm/page_isolation.c > > > > > > @@ -274,7 +274,7 @@ __test_page_isolated_in_pageblock(unsigned long pfn, unsigned long end_pfn, > > > > > > * simple way to verify that as VM_BUG_ON(), though. > > > > > > */ > > > > > > pfn += 1 << page_order(page); > > > > > > - else if (skip_hwpoisoned_pages && PageHWPoison(page)) > > > > > > + else if (skip_hwpoisoned_pages && PageHWPoison(compound_head(page))) > > > > > > /* A HWPoisoned page cannot be also PageBuddy */ > > > > > > pfn++; > > > > > > else > > > > > > > > > > This fix looks good to me. The original code only addresses hwpoisoned 4kB-page, > > > > > we seem to have this issue since the following commit, > > > > > > > > Thanks a lot for double checking Naoya! > > > > > > > > > commit b023f46813cde6e3b8a8c24f432ff9c1fd8e9a64 > > > > > Author: Wen Congyang > > > > > Date: Tue Dec 11 16:00:45 2012 -0800 > > > > > > > > > > memory-hotplug: skip HWPoisoned page when offlining pages > > > > > > > > > > and extension of LTP coverage finally discovered this. > > > > > > > > Qian, could you give the patch some testing? > > > > > > Unfortunately, this does not solve the problem.?It looks to me that in > > > soft_offline_huge_page(), set_hwpoison_free_buddy_page() will only set > > > PG_hwpoison for buddy pages, so the even the compound_head() has no PG_hwpoison > > > set. > > > > > > if (PageBuddy(page_head) && page_order(page_head) >= order) { > > > if (!TestSetPageHWPoison(page)) > > > hwpoisoned = true; > > > > This is more than unexpected. How are we supposed to find out that the > > page is poisoned? Any idea Naoya? > > # sorry for my poor review... > > We set PG_hwpoison bit only on the head page for hugetlb, that's because > we handle multiple pages as a single one for hugetlb. So it's enough > to check isolation only on the head page. Simply skipping pfn cursor to > the page after the hugepage should avoid the infinite loop: But the page dump Qian provided shows that the head page doesn't have HWPoison bit either. If it had then going pfn at a time should just work because all tail pages would be skipped. Or do I miss something? > @@ -274,9 +274,13 @@ __test_page_isolated_in_pageblock(unsigned long pfn, unsigned long end_pfn, > * simple way to verify that as VM_BUG_ON(), though. > */ > pfn += 1 << page_order(page); > - else if (skip_hwpoisoned_pages && PageHWPoison(page)) > - /* A HWPoisoned page cannot be also PageBuddy */ > - pfn++; > + else if (skip_hwpoisoned_pages && PageHWPoison(compound_head(page))) > + /* > + * A HWPoisoned page cannot be also PageBuddy. > + * PG_hwpoison could be set only on the head page in > + * hugetlb case, so no need to check tail pages. > + */ > + pfn += 1 << compound_order(page); > else > break; > } > > Qian, could you please try this? > > Thanks, > Naoya Horiguchi -- Michal Hocko SUSE Labs