Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10429712imu; Thu, 6 Dec 2018 00:33:23 -0800 (PST) X-Google-Smtp-Source: AFSGD/XtZ4p1hF6ZeT4y0bN5tRx/rs/M2qqvDTF/Z5xj5njMqzmDsqOqv5f9THC8tKkDhqmsqXsI X-Received: by 2002:a17:902:7e4f:: with SMTP id a15mr26806158pln.149.1544085203726; Thu, 06 Dec 2018 00:33:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544085203; cv=none; d=google.com; s=arc-20160816; b=XF4nVT0SWN7v/dFS0ccCPSBj7LdQPUHtKCKDYLA5ufdabTUQ9dql5+R/09WmOgmkzr ZwL+QbkO61AiCBxy3+RRhM4Y9tV0eJI2RPbSnD09yl27wEUWM5yEru4RSbwFPw5wxcCZ hL9W0uc2PnlA8G30sruAAqwIXlrCawz4iLaibmHlWDlqxJic2ZBrQKE5kXw1AHz0fiyU HZoM5ro3fsSJ1ucPxmHTnd55zf942kUjsVZZz6Q4rpWxkMWIINxZaYjvphsAm+fZkbl9 nANhM5PNkCJ2wwu+FCtP+s8NqvKJ46k/mp2MeNpOVKKiM2SXR3NcnvfYn9DshCrhBOoI n7BQ== 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; bh=kRlOr+OwPBW4NVwrBWQgq/e2l8HGPdBXHY1DAOmfEPk=; b=yx1CRiAlkajkzYnDOxNyjcomNZDjrNjJCx8kqKJDuprs+qxcnOY1H8cQDq+jLtDII/ Gfxl0dbczPpWOpWtOnGjOAtckWOfG/lT08p23eQm+Ds3SP3l08eCVqQoD37wpPD9XvRY rTf3R/R7cLWPOozN0frwfHExYKucxMM7dGj+5/EhvWFAm0cHn7ZFvqhKJzhtR7Uw7p6O HYumQ1EGN6IOq+zuA6COQ7563pp1JT27lvrRQtM4noIIfl3bUBOpW5QWIu5pGfNx8VMp HrzelAyAA64HY6k9VtuFCU2vwpsPYtUC5zGKjhVvLaSyGiGV7ePZbYerssEibMrF7tmz ohlw== 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 9si21705009plc.40.2018.12.06.00.33.08; Thu, 06 Dec 2018 00:33:23 -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; 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 S1729302AbeLFIcK (ORCPT + 99 others); Thu, 6 Dec 2018 03:32:10 -0500 Received: from mx2.suse.de ([195.135.220.15]:44044 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727575AbeLFIcK (ORCPT ); Thu, 6 Dec 2018 03:32:10 -0500 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 0739AAD75; Thu, 6 Dec 2018 08:32:07 +0000 (UTC) Date: Thu, 6 Dec 2018 09:32:06 +0100 From: Michal Hocko To: Naoya Horiguchi Cc: Oscar Salvador , Andrew Morton , Dan Williams , Pavel Tatashin , "linux-mm@kvack.org" , LKML , Stable tree Subject: Re: [RFC PATCH] hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined Message-ID: <20181206083206.GC1286@dhcp22.suse.cz> References: <20181203100309.14784-1-mhocko@kernel.org> <20181205122918.GL1286@dhcp22.suse.cz> <20181205165716.GS1286@dhcp22.suse.cz> <20181206052137.GA28595@hori1.linux.bs1.fc.nec.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181206052137.GA28595@hori1.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 Thu 06-12-18 05:21:38, Naoya Horiguchi wrote: > On Wed, Dec 05, 2018 at 05:57:16PM +0100, Michal Hocko wrote: > > On Wed 05-12-18 13:29:18, Michal Hocko wrote: > > [...] > > > After some more thinking I am not really sure the above reasoning is > > > still true with the current upstream kernel. Maybe I just managed to > > > confuse myself so please hold off on this patch for now. Testing by > > > Oscar has shown this patch is helping but the changelog might need to be > > > updated. > > > > OK, so Oscar has nailed it down and it seems that 4.4 kernel we have > > been debugging on behaves slightly different. The underlying problem is > > the same though. So I have reworded the changelog and added "just in > > case" PageLRU handling. Naoya, maybe you have an argument that would > > make this void for current upstream kernels. > > The following commit (not in 4.4.x stable tree) might explain the > difference you experienced: > > commit 286c469a988fbaf68e3a97ddf1e6c245c1446968 > Author: Naoya Horiguchi > Date: Wed May 3 14:56:22 2017 -0700 > > mm: hwpoison: call shake_page() after try_to_unmap() for mlocked page > > This commit adds shake_page() for mlocked pages to make sure that the target > page is flushed out from LRU cache. Without this shake_page(), subsequent > delete_from_lru_cache() (from me_pagecache_clean()) fails to isolate it and > the page will finally return back to LRU list. So this scenario leads to > "hwpoisoned by still linked to LRU list" page. OK, I see. So does that mean that the LRU handling is no longer needed and there is a guanratee that all kernels with the above commit cannot ever get an LRU page? -- Michal Hocko SUSE Labs