Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 29 Mar 2022 21:13:27 +0200
From:   Oscar Salvador <osalvador@suse.de>
To:     Rik van Riel <riel@surriel.com>
Cc:     linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        kernel-team@fb.com, Miaohe Lin <linmiaohe@huawei.com>,
        Naoya Horiguchi <naoya.horiguchi@nec.com>,
        Mel Gorman <mgorman@suse.de>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        stable@vger.kernel.org
Subject: Re: [PATCH] mm,hwpoison: unmap poisoned page before invalidation
Message-ID: <YkNaVxe5Vso9DGl+@localhost.localdomain>
References: <20220325161428.5068d97e@imladris.surriel.com>
 <YkF5Jd6fauTRvVVg@localhost.localdomain>
 <47936edb3b0f9c9f04f0d0d2e7f38383a22b6a3d.camel@surriel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47936edb3b0f9c9f04f0d0d2e7f38383a22b6a3d.camel@surriel.com>
Precedence: bulk

On Tue, Mar 29, 2022 at 11:49:53AM -0400, Rik van Riel wrote:

> It results in us returning to userspace as if the page
> fault had been handled, resulting in a second fault on
> the same address.
> 
> However, now the page is no longer in the page cache,
> and we can read it in from disk, to a page that is not
> hardware poisoned, and we can then use that second page
> without issues.

Ok, I see, thanks a lot for the explanation Rik.


-- 
Oscar Salvador
SUSE Labs