From: Rik van Riel <riel@surriel.com>
To: David Hildenbrand <david@redhat.com>, linux-kernel@vger.kernel.org
Cc: kernel-team@fb.com, linux-mm@kvack.org,
Miaohe Lin <linmiaohe@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2] mm: clean up hwpoison page cache page in fault path
Date: Tue, 15 Feb 2022 10:01:20 -0500 [thread overview]
Message-ID: <63f930e411655a6ad37d4818d0ae19784c82f076.camel@surriel.com> (raw)
In-Reply-To: <2a881586-3f5e-c277-f373-a9014d631700@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Tue, 2022-02-15 at 12:22 +0100, David Hildenbrand wrote:
> On 13.02.22 03:37, Rik van Riel wrote:
> > Sometimes the page offlining code can leave behind a hwpoisoned
> > clean
> > page cache page. This can lead to programs being killed over and
> > over
> > and over again as they fault in the hwpoisoned page, get killed,
> > and
> > then get re-spawned by whatever wanted to run them.
>
> Hi Rik,
>
> am I correct that you are only talking about soft offlining as
> triggered
> from mm/memory-failure.c, not page offlining as in memory offlining
> mm/memory_hotunplug.c ?
That is correct in that I am talking only about memory-failure.c,
however the code in memory-failure.c has both hard and soft
offlining modes, and I suppose this patch covers both?
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-15 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 2:37 [PATCH v2] mm: clean up hwpoison page cache page in fault path Rik van Riel
2022-02-14 23:24 ` Andrew Morton
2022-02-15 1:37 ` Rik van Riel
2022-02-15 5:15 ` HORIGUCHI NAOYA(堀口 直也)
2022-02-15 11:22 ` David Hildenbrand
2022-02-15 15:01 ` Rik van Riel [this message]
2022-02-15 15:06 ` David Hildenbrand
2022-02-15 12:51 ` Oscar Salvador
2022-02-15 15:04 ` Rik van Riel
2022-02-16 2:13 ` Miaohe Lin
2022-02-21 12:54 ` Oscar Salvador
2022-02-21 13:19 ` Miaohe Lin
2022-02-21 12:55 ` Oscar Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63f930e411655a6ad37d4818d0ae19784c82f076.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).