linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <shy828301@gmail.com>
To: hughd@google.com, willy@infradead.org, jhubbard@nvidia.com,
	kirill.shutemov@linux.intel.com, vbabka@suse.cz,
	akpm@linux-foundation.org
Cc: shy828301@gmail.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] mm: dump_page: print total mapcount for compound page
Date: Fri, 28 May 2021 10:54:03 -0700	[thread overview]
Message-ID: <20210528175403.4506-1-shy828301@gmail.com> (raw)

The total mapcount is a useful information for debugging, but we can't
call total_mapcount() directly since it calls some assertions which may
be triggered as commit 6dc5ea16c86f ("mm,
dump_page: do not crash with bad compound_mapcount()") met.

We could implement yet another implementation for dump_page() but
it has the limitation when individual mapcount of subpages is corrupted.

Actually the total mapcount could be decoded from refcount, pincount and
compound mapcount although it may be not very precise due to some
transient references.

Signed-off-by: Yang Shi <shy828301@gmail.com>
---
I think we are on the same page that the total mapcount is useful
information and it would be ideal to print this information when dumpping
page if possible.  But how to implement it safely seems controversial.
Some ideas and potential problems have been discussed by
https://lore.kernel.org/linux-mm/alpine.LSU.2.11.2105261733110.16920@eggly.anvils/.

So I prepared this patch to show a possible approach to get some
feedback.  The same thing could be decoded by the reader of page dump
as well by using the same formula used by this patch.  However it sounds
more convenient to have kernel do the math.
 
 mm/debug.c | 35 +++++++++++++++++++++++++++++------
 1 file changed, 29 insertions(+), 6 deletions(-)

diff --git a/mm/debug.c b/mm/debug.c
index e73fe0a8ec3d..129efcfcaf79 100644
--- a/mm/debug.c
+++ b/mm/debug.c
@@ -54,8 +54,13 @@ static void __dump_page(struct page *page)
 	 * inaccuracy here due to racing.
 	 */
 	bool page_cma = is_migrate_cma_page(page);
-	int mapcount;
+	int mapcount, total_mapcount;
+	int nr;
+	int refcount;
+	int pincount = 0;
+	int comp_mapcnt;
 	char *type = "";
+	bool is_slab = PageSlab(head);
 
 	if (page < head || (page >= head + MAX_ORDER_NR_PAGES)) {
 		/*
@@ -82,22 +87,40 @@ static void __dump_page(struct page *page)
 	 * page->_mapcount space in struct page is used by sl[aou]b pages to
 	 * encode own info.
 	 */
-	mapcount = PageSlab(head) ? 0 : page_mapcount(page);
+	mapcount = is_slab ? 0 : page_mapcount(page);
+
+	refcount = page_ref_count(head);
 
 	pr_warn("page:%p refcount:%d mapcount:%d mapping:%p index:%#lx pfn:%#lx\n",
-			page, page_ref_count(head), mapcount, mapping,
+			page, refcount, mapcount, mapping,
 			page_to_pgoff(page), page_to_pfn(page));
 	if (compound) {
+		comp_mapcnt = head_compound_mapcount(head);
 		if (hpage_pincount_available(page)) {
+			pincount = head_compound_pincount(head);
 			pr_warn("head:%p order:%u compound_mapcount:%d compound_pincount:%d\n",
 					head, compound_order(head),
-					head_compound_mapcount(head),
-					head_compound_pincount(head));
+					comp_mapcnt, pincount);
 		} else {
 			pr_warn("head:%p order:%u compound_mapcount:%d\n",
 					head, compound_order(head),
-					head_compound_mapcount(head));
+					comp_mapcnt);
+		}
+
+		nr = compound_nr(head);
+		if (is_slab)
+			total_mapcount = 0;
+		else if (PageHuge(head))
+			total_mapcount = comp_mapcnt;
+		else {
+			if (mapping) {
+				if (!PageAnon(head))
+					nr = nr * (comp_mapcnt + 1) - comp_mapcnt;
+			} else
+				nr = 0;
+			total_mapcount = refcount - pincount - nr;
 		}
+		pr_warn("total_mapcount(estimated):%d\n", total_mapcount);
 	}
 
 #ifdef CONFIG_MEMCG
-- 
2.26.2


             reply	other threads:[~2021-05-28 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 17:54 Yang Shi [this message]
2021-05-28 18:22 ` [RFC PATCH] mm: dump_page: print total mapcount for compound page Matthew Wilcox
2021-05-28 18:56   ` Yang Shi
2021-05-28 18:26 ` John Hubbard
2021-05-28 19:03   ` Yang Shi
2021-05-28 19:59     ` John Hubbard
2021-05-28 19:47 ` Hugh Dickins
2021-05-31  8:19   ` Kirill A. Shutemov

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=20210528175403.4506-1-shy828301@gmail.com \
    --to=shy828301@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --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).