linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jiaqi Yan <jiaqiyan@google.com>
To: Kyle Meyer <kyle.meyer@hpe.com>
Cc: akpm@linux-foundation.org, linmiaohe@huawei.com,
	jane.chu@oracle.com,  bp@alien8.de, david@redhat.com,
	Liam.Howlett@oracle.com,  linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 lorenzo.stoakes@oracle.com, mhocko@suse.com,
	nao.horiguchi@gmail.com,  osalvador@suse.de, rppt@kernel.org,
	russ.anderson@hpe.com, surenb@google.com,  tony.luck@intel.com,
	vbabka@suse.cz
Subject: Re: [PATCH v2] mm/memory-failure: Fix redundant updates for already poisoned pages
Date: Thu, 28 Aug 2025 12:58:50 -0700	[thread overview]
Message-ID: <CACw3F50kFq4V9+-JUdi+PEYbNUkOJZHPOy4VCowhKXW-sB=Ugw@mail.gmail.com> (raw)
In-Reply-To: <aLCiHMy12Ck3ouwC@hpe.com>

On Thu, Aug 28, 2025 at 11:38 AM Kyle Meyer <kyle.meyer@hpe.com> wrote:
>
> Duplicate memory errors can be reported by multiple sources.
>
> Passing an already poisoned page to action_result() causes issues:
>
> * The amount of hardware corrupted memory is incorrectly updated.
> * Per NUMA node MF stats are incorrectly updated.
> * Redundant "already poisoned" messages are printed.
>
> Avoid those issues by:
>
> * Skipping hardware corrupted memory updates for already poisoned pages.
> * Skipping per NUMA node MF stats updates for already poisoned pages.
> * Dropping redundant "already poisoned" messages.
>
> Make MF_MSG_ALREADY_POISONED consistent with other action_page_types and
> make calls to action_result() consistent for already poisoned
> normal pages and huge pages.
>
> Fixes: b8b9488d50b7 ("mm/memory-failure: improve memory failure action_result messages")
> Signed-off-by: Kyle Meyer <kyle.meyer@hpe.com>
> ---
>
> v1 -> v2:
>  * Continue passing poisoned pages to action_result() with MF_FAILED but don't
> update anything.
>  * https://lore.kernel.org/all/20250821164445.14467-1-kyle.meyer@hpe.com
>
> ---
>  mm/memory-failure.c | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index fc30ca4804bf..10b3c281c2ae 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -956,7 +956,7 @@ static const char * const action_page_types[] = {
>         [MF_MSG_BUDDY]                  = "free buddy page",
>         [MF_MSG_DAX]                    = "dax page",
>         [MF_MSG_UNSPLIT_THP]            = "unsplit thp",
> -       [MF_MSG_ALREADY_POISONED]       = "already poisoned",
> +       [MF_MSG_ALREADY_POISONED]       = "already poisoned page",
>         [MF_MSG_UNKNOWN]                = "unknown page",
>  };
>
> @@ -1349,9 +1349,10 @@ static int action_result(unsigned long pfn, enum mf_action_page_type type,
>  {
>         trace_memory_failure_event(pfn, type, result);
>
> -       num_poisoned_pages_inc(pfn);
> -
> -       update_per_node_mf_stats(pfn, result);
> +       if (type != MF_MSG_ALREADY_POISONED) {
> +               num_poisoned_pages_inc(pfn);
> +               update_per_node_mf_stats(pfn, result);
> +       }

Thanks Kyle, the code looks good to me. While you wait for Miaohe's
review/ack...

Reviewed-by: Jiaqi Yan <jiaqiyan@google.com>

>
>         pr_err("%#lx: recovery action for %s: %s\n",
>                 pfn, action_page_types[type], action_name[result]);
> @@ -2094,12 +2095,11 @@ static int try_memory_failure_hugetlb(unsigned long pfn, int flags, int *hugetlb
>                 *hugetlb = 0;
>                 return 0;
>         } else if (res == -EHWPOISON) {
> -               pr_err("%#lx: already hardware poisoned\n", pfn);
>                 if (flags & MF_ACTION_REQUIRED) {
>                         folio = page_folio(p);
>                         res = kill_accessing_process(current, folio_pfn(folio), flags);
> -                       action_result(pfn, MF_MSG_ALREADY_POISONED, MF_FAILED);
>                 }
> +               action_result(pfn, MF_MSG_ALREADY_POISONED, MF_FAILED);
>                 return res;
>         } else if (res == -EBUSY) {
>                 if (!(flags & MF_NO_RETRY)) {
> @@ -2285,7 +2285,6 @@ int memory_failure(unsigned long pfn, int flags)
>                 goto unlock_mutex;
>
>         if (TestSetPageHWPoison(p)) {
> -               pr_err("%#lx: already hardware poisoned\n", pfn);
>                 res = -EHWPOISON;
>                 if (flags & MF_ACTION_REQUIRED)
>                         res = kill_accessing_process(current, pfn, flags);
> --
> 2.50.1
>


  reply	other threads:[~2025-08-28 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 18:38 Kyle Meyer
2025-08-28 19:58 ` Jiaqi Yan [this message]
2025-08-28 20:16 ` David Hildenbrand
2025-08-28 22:53 ` jane.chu
2025-08-29  6:35 ` 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='CACw3F50kFq4V9+-JUdi+PEYbNUkOJZHPOy4VCowhKXW-sB=Ugw@mail.gmail.com' \
    --to=jiaqiyan@google.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=david@redhat.com \
    --cc=jane.chu@oracle.com \
    --cc=kyle.meyer@hpe.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=russ.anderson@hpe.com \
    --cc=surenb@google.com \
    --cc=tony.luck@intel.com \
    --cc=vbabka@suse.cz \
    /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