linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <shy828301@gmail.com>
To: Stefan Roesch <shr@devkernel.io>
Cc: kernel-team@fb.com, akpm@linux-foundation.org,
	hannes@cmpxchg.org,  riel@surriel.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 stable@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v3] mm: Fix for negative counter: nr_file_hugepages
Date: Mon, 13 Nov 2023 17:42:37 -0800	[thread overview]
Message-ID: <CAHbLzkqx9A2XoPJynr4JR-31UstASW-bgym4PM9mok7gUOSM3A@mail.gmail.com> (raw)
In-Reply-To: <20231108171517.2436103-1-shr@devkernel.io>

On Wed, Nov 8, 2023 at 9:15 AM Stefan Roesch <shr@devkernel.io> wrote:
>
> While qualifiying the 6.4 release, the following warning was detected in
> messages:
>
> vmstat_refresh: nr_file_hugepages -15664
>
> The warning is caused by the incorrect updating of the NR_FILE_THPS
> counter in the function split_huge_page_to_list. The if case is checking
> for folio_test_swapbacked, but the else case is missing the check for
> folio_test_pmd_mappable. The other functions that manipulate the counter
> like __filemap_add_folio and filemap_unaccount_folio have the
> corresponding check.
>
> I have a test case, which reproduces the problem. It can be found here:
>   https://github.com/sroeschus/testcase/blob/main/vmstat_refresh/madv.c
>
> The test case reproduces on an XFS filesystem. Running the same test
> case on a BTRFS filesystem does not reproduce the problem.
>
> AFAIK version 6.1 until 6.6 are affected by this problem.
>
> Signed-off-by: Stefan Roesch <shr@devkernel.io>
> Co-debugged-by: Johannes Weiner <hannes@cmpxchg.org>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Cc: stable@vger.kernel.org

Reviewed-by: Yang Shi <shy828301@gmail.com>

> ---
>  mm/huge_memory.c | 16 +++++++++-------
>  1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index 064fbd90822b4..874000f97bfc1 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -2737,13 +2737,15 @@ int split_huge_page_to_list(struct page *page, struct list_head *list)
>                         int nr = folio_nr_pages(folio);
>
>                         xas_split(&xas, folio, folio_order(folio));
> -                       if (folio_test_swapbacked(folio)) {
> -                               __lruvec_stat_mod_folio(folio, NR_SHMEM_THPS,
> -                                                       -nr);
> -                       } else {
> -                               __lruvec_stat_mod_folio(folio, NR_FILE_THPS,
> -                                                       -nr);
> -                               filemap_nr_thps_dec(mapping);
> +                       if (folio_test_pmd_mappable(folio)) {
> +                               if (folio_test_swapbacked(folio)) {
> +                                       __lruvec_stat_mod_folio(folio,
> +                                                       NR_SHMEM_THPS, -nr);
> +                               } else {
> +                                       __lruvec_stat_mod_folio(folio,
> +                                                       NR_FILE_THPS, -nr);
> +                                       filemap_nr_thps_dec(mapping);
> +                               }
>                         }
>                 }
>
>
> base-commit: ffc253263a1375a65fa6c9f62a893e9767fbebfa
> --
> 2.39.3
>
>


      parent reply	other threads:[~2023-11-14  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 17:15 Stefan Roesch
2023-11-08 17:29 ` Matthew Wilcox
2023-11-08 17:38 ` David Hildenbrand
2023-11-14  1:42 ` Yang Shi [this message]

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=CAHbLzkqx9A2XoPJynr4JR-31UstASW-bgym4PM9mok7gUOSM3A@mail.gmail.com \
    --to=shy828301@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@surriel.com \
    --cc=shr@devkernel.io \
    --cc=stable@vger.kernel.org \
    --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