Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10435289imu; Thu, 6 Dec 2018 00:41:29 -0800 (PST) X-Google-Smtp-Source: AFSGD/WmAPk0n63p3ML5djSURLjrWkeNADXnBnG12Z1UlFBnVqo/lACoUbBsvB6UhtYSoYG2u+rV X-Received: by 2002:a63:151f:: with SMTP id v31mr22949407pgl.34.1544085689661; Thu, 06 Dec 2018 00:41:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544085689; cv=none; d=google.com; s=arc-20160816; b=y3y7wQJkzhAtcqjOFV2d9m9GzoUt1DqpcAWzKGrYbLAjUAbaAl1nsKjwMZyOPRetYM k6nZhnvFrgcKJLpq3yMYAkqNgQ1JmgGtsHTNv+KtHzE7DgCWJvNb5KC6e2kUZB6jC2yq lLgffHJCx0g0+anYwzMedheHLGsBwkL4M5RAOw8jbnxfhoUUgSYkktlxM6I1ROapLkE3 HtJetvionhvTHr9tdtGb4hj9XaNwQ/y+FaaZm+EGmKaoUXsDQZkku2E0Wefnz+hqx5n3 NfmJaS9BEtf58lxJk6NgtKIoajvXR/FnAxncC0bnPAr6Xhs+Kac5j6NPzIX6ZUar+s0V KuOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version; bh=JwHvZ8ntxHWbBdBGJXfnbm5NZ7FMx5Fk4XC5Zpd1vRE=; b=gsMDa+NDAvu/Xzjjvyul8yGmtfHUB9aIbVFnV4jigMw8AwlpiY++0AOYlTFDW7sIp5 1AYIjFh0WVuiITycY/ObQ3gooZxnCr2Cm9AtnAShkl8IQIsyxzIFy5dm03cd4UWfg9Bw Bcmq7jtkwYqoDiTRBvj22IiNBix7QF9pAUHX6FK8iDm+B5tEcEKPjidniHyWCzzhZtQC KtaSFLvIgvFPz75hAxG5MSCYHqf1WDzDG+JIP4fkMj99+i8cz8Rj0cq+Xe7kSFEw0nKb ZIeB9anstMwwbIinq4cD+EGADuqtfISoLPW7PVFIUXI7nO3VlKXQQlJzSSbW+iTyc4fY RLFA== 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 k18si308622pgf.97.2018.12.06.00.41.13; Thu, 06 Dec 2018 00:41:29 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729132AbeLFIk0 (ORCPT + 99 others); Thu, 6 Dec 2018 03:40:26 -0500 Received: from mx2.suse.de ([195.135.220.15]:46484 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727832AbeLFIkZ (ORCPT ); Thu, 6 Dec 2018 03:40:25 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id EBDCAADE6; Thu, 6 Dec 2018 08:40:23 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 06 Dec 2018 09:40:23 +0100 From: osalvador@suse.de To: Michal Hocko Cc: Naoya Horiguchi , Oscar Salvador , Andrew Morton , Dan Williams , Pavel Tatashin , linux-mm@kvack.org, LKML , Stable tree , owner-linux-mm@kvack.org Subject: Re: [RFC PATCH] hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined In-Reply-To: <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> <20181206083206.GC1286@dhcp22.suse.cz> Message-ID: X-Sender: osalvador@suse.de User-Agent: Roundcube Webmail Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> 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? For the sake of completeness: I made a quick test reverting 286c469a988 on upstream kernel. As expected, the poisoned page is in LRU when it hits do_migrate_range, and so, the migration path is taken and I see the exact failure I saw on. 4.4 Oscar Salvador --- Suse L3