[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210331060739.GW351017@casper.infradead.org>
Date: Wed, 31 Mar 2021 07:07:39 +0100
From: Matthew Wilcox <willy@...radead.org>
To: HORIGUCHI NAOYA(堀口 直也)
<naoya.horiguchi@....com>
Cc: David Hildenbrand <david@...hat.com>,
Aili Yao <yaoaili@...gsoft.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yangfeng1@...gsoft.com" <yangfeng1@...gsoft.com>,
"sunhao2@...gsoft.com" <sunhao2@...gsoft.com>,
Oscar Salvador <osalvador@...e.de>,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: Re: [PATCH v5] mm/gup: check page hwposion status for coredump.
On Wed, Mar 31, 2021 at 01:52:59AM +0000, HORIGUCHI NAOYA(堀口 直也) wrote:
> If we successfully unmapped but failed in truncate_error_page() for example,
> the processes mapping the page would get -EFAULT as expected. But even in
> this case, other processes could reach the error page via page cache and
> __get_user_pages_locked() for them could return the hwpoisoned page.
How would that happen? We check PageHWPoison before inserting a page
into the page tables. See, eg, filemap_map_pages() and __do_fault().
Powered by blists - more mailing lists