From: Miaohe Lin <linmiaohe@huawei.com>
To: Jane Chu <jane.chu@oracle.com>, <nao.horiguchi@gmail.com>,
<akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] mm/memory-failure: send SIGBUS in the event of thp split fail
Date: Sun, 5 May 2024 15:00:20 +0800 [thread overview]
Message-ID: <038cffc0-e027-b518-460f-40099819c588@huawei.com> (raw)
In-Reply-To: <20240501232458.3919593-4-jane.chu@oracle.com>
On 2024/5/2 7:24, Jane Chu wrote:
> When handle hwpoison in a GUP longterm pin'ed thp page,
> try_to_split_thp_page() will fail. And at this point, there is little else
> the kernel could do except sending a SIGBUS to the user process, thus
> give it a chance to recover.
>
> Signed-off-by: Jane Chu <jane.chu@oracle.com>
Thanks for your patch. Some comments below.
> ---
> mm/memory-failure.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 7fcf182abb96..67f4d24a98e7 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -2168,6 +2168,37 @@ static int memory_failure_dev_pagemap(unsigned long pfn, int flags,
> return rc;
> }
>
> +/*
> + * The calling condition is as such: thp split failed, page might have
> + * been GUP longterm pinned, not much can be done for recovery.
> + * But a SIGBUS should be delivered with vaddr provided so that the user
> + * application has a chance to recover. Also, application processes'
> + * election for MCE early killed will be honored.
> + */
> +static int kill_procs_now(struct page *p, unsigned long pfn, int flags,
> + struct page *hpage)
> +{
> + struct folio *folio = page_folio(hpage);
> + LIST_HEAD(tokill);
> + int res = -EHWPOISON;
> +
> + /* deal with user pages only */
> + if (PageReserved(p) || PageSlab(p) || PageTable(p) || PageOffline(p))
> + res = -EBUSY;
> + if (!(PageLRU(hpage) || PageHuge(p)))
> + res = -EBUSY;
Above checks seems unneeded. We already know it's thp?
> +
> + if (res == -EHWPOISON) {
> + collect_procs(folio, p, &tokill, flags & MF_ACTION_REQUIRED);
> + kill_procs(&tokill, true, pfn, flags);
> + }
> +
> + if (flags & MF_COUNT_INCREASED)
> + put_page(p);
This if block is broken. put_page() has been done when try_to_split_thp_page() fails?
> +
action_result is missing?
> + return res;
> +}
> +
> /**
> * memory_failure - Handle memory failure of a page.
> * @pfn: Page Number of the corrupted page
> @@ -2297,6 +2328,11 @@ int memory_failure(unsigned long pfn, int flags)
> */
> SetPageHasHWPoisoned(hpage);
> if (try_to_split_thp_page(p) < 0) {
Should hwpoison_filter() be called in this case?
> + if (flags & MF_ACTION_REQUIRED) {
> + pr_err("%#lx: thp split failed\n", pfn);
> + res = kill_procs_now(p, pfn, flags, hpage);
Can we use hwpoison_user_mappings() directly here?
Thanks.
.
> + goto unlock_mutex;
> + }
> res = action_result(pfn, MF_MSG_UNSPLIT_THP, MF_IGNORED);
> goto unlock_mutex;
> }
>
next prev parent reply other threads:[~2024-05-05 7:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 23:24 [PATCH 0/3] Enhance soft hwpoison handling and injection Jane Chu
2024-05-01 23:24 ` [PATCH 1/3] mm/memory-failure: try to send SIGBUS even if unmap failed Jane Chu
2024-05-07 9:02 ` Oscar Salvador
2024-05-07 17:54 ` Jane Chu
2024-05-08 12:06 ` Oscar Salvador
2024-05-08 16:51 ` Jane Chu
2024-05-08 7:47 ` Miaohe Lin
2024-05-08 16:58 ` Jane Chu
2024-05-09 2:54 ` Miaohe Lin
2024-05-09 16:40 ` Jane Chu
2024-05-01 23:24 ` [PATCH 2/3] mm/madvise: Add MF_ACTION_REQUIRED to madvise(MADV_HWPOISON) Jane Chu
2024-05-05 7:02 ` Miaohe Lin
2024-05-06 19:54 ` Jane Chu
2024-05-08 7:58 ` Miaohe Lin
2024-05-01 23:24 ` [PATCH 3/3] mm/memory-failure: send SIGBUS in the event of thp split fail Jane Chu
2024-05-05 7:00 ` Miaohe Lin [this message]
2024-05-06 20:26 ` Jane Chu
2024-05-08 8:08 ` Miaohe Lin
2024-05-08 17:45 ` Jane Chu
2024-05-09 8:30 ` Miaohe Lin
2024-05-09 15:34 ` Jane Chu
2024-05-10 2:59 ` Miaohe Lin
2024-05-10 3:18 ` Jane Chu
2024-05-08 9:03 ` Miaohe Lin
2024-05-08 16:56 ` Jane Chu
2024-05-09 8:52 ` Miaohe Lin
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=038cffc0-e027-b518-460f-40099819c588@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=jane.chu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
/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