From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,yosryahmed@google.com,david@redhat.com,hughd@google.com,akpm@linux-foundation.org
Subject: [folded-merged] mm-rmap-abstract-updating-per-node-and-per-memcg-stats-fix.patch removed from -mm tree
Date: Mon, 24 Jun 2024 21:19:07 -0700 [thread overview]
Message-ID: <20240625041907.B0A50C4AF0B@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: rmap: abstract updating per-node and per-memcg stats fix
has been removed from the -mm tree. Its filename was
mm-rmap-abstract-updating-per-node-and-per-memcg-stats-fix.patch
This patch was dropped because it was folded into mm-rmap-abstract-updating-per-node-and-per-memcg-stats.patch
------------------------------------------------------
From: Hugh Dickins <hughd@google.com>
Subject: mm: rmap: abstract updating per-node and per-memcg stats fix
Date: Tue, 11 Jun 2024 22:10:43 -0700 (PDT)
/proc/meminfo is showing ridiculously large numbers on some lines:
__folio_remove_rmap()'s __folio_mod_stat() should be subtracting!
Link: https://lkml.kernel.org/r/49914517-dfc7-e784-fde0-0e08fafbecc2@google.com
Signed-off-by: Hugh Dickins <hughd@google.com>
Reviewed-by: Yosry Ahmed <yosryahmed@google.com>
Acked-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/rmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/rmap.c~mm-rmap-abstract-updating-per-node-and-per-memcg-stats-fix
+++ a/mm/rmap.c
@@ -1567,7 +1567,7 @@ static __always_inline void __folio_remo
list_empty(&folio->_deferred_list))
deferred_split_folio(folio);
}
- __folio_mod_stat(folio, nr, nr_pmdmapped);
+ __folio_mod_stat(folio, -nr, -nr_pmdmapped);
/*
* It would be tidy to reset folio_test_anon mapping when fully
_
Patches currently in -mm which might be from hughd@google.com are
mm-rmap-abstract-updating-per-node-and-per-memcg-stats.patch
reply other threads:[~2024-06-25 4:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240625041907.B0A50C4AF0B@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=yosryahmed@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.