From: Matthew Wilcox <willy@infradead.org>
To: linux-mm@kvack.org
Cc: Matthew Wilcox <mawilcox@microsoft.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/4] mm: Mark pages allocated through vmalloc
Date: Wed, 28 Feb 2018 14:31:56 -0800 [thread overview]
Message-ID: <20180228223157.9281-4-willy@infradead.org> (raw)
In-Reply-To: <20180228223157.9281-1-willy@infradead.org>
From: Matthew Wilcox <mawilcox@microsoft.com>
Use a bit in page_type to mark pages which have been allocated through
vmalloc. This can be helpful when debugging or analysing crashdumps.
Signed-off-by: Matthew Wilcox <mawilcox@microsoft.com>
---
include/linux/page-flags.h | 6 ++++++
mm/vmalloc.c | 2 ++
2 files changed, 8 insertions(+)
diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index d151f590bbc6..8142ab716e90 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -643,6 +643,7 @@ PAGEFLAG_FALSE(DoubleMap)
#define PG_buddy 0x00000080
#define PG_balloon 0x00000100
#define PG_kmemcg 0x00000200
+#define PG_vmalloc 0x00000400
#define PageType(page, flag) \
((page->page_type & (PAGE_TYPE_BASE | flag)) == PAGE_TYPE_BASE)
@@ -681,6 +682,11 @@ PAGE_TYPE_OPS(Balloon, balloon)
*/
PAGE_TYPE_OPS(Kmemcg, kmemcg)
+/*
+ * Pages allocated through vmalloc are tagged with this bit.
+ */
+PAGE_TYPE_OPS(Vmalloc, vmalloc)
+
extern bool is_free_buddy_page(struct page *page);
__PAGEFLAG(Isolated, isolated, PF_ANY);
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index ebff729cc956..3bc0538fc21b 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -1536,6 +1536,7 @@ static void __vunmap(const void *addr, int deallocate_pages)
struct page *page = area->pages[i];
BUG_ON(!page);
+ __ClearPageVmalloc(page);
__free_pages(page, 0);
}
@@ -1705,6 +1706,7 @@ static void *__vmalloc_area_node(struct vm_struct *area, gfp_t gfp_mask,
area->nr_pages = i;
goto fail;
}
+ __SetPageVmalloc(page);
area->pages[i] = page;
if (gfpflags_allow_blocking(gfp_mask|highmem_mask))
cond_resched();
--
2.16.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-28 22:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 22:31 [PATCH v3 0/4] Split page_type out from mapcount Matthew Wilcox
2018-02-28 22:31 ` [PATCH v3 1/4] s390: Use _refcount for pgtables Matthew Wilcox
2018-03-01 12:53 ` Kirill A. Shutemov
2018-03-01 14:04 ` Martin Schwidefsky
2018-03-01 14:28 ` Kirill A. Shutemov
2018-03-01 14:39 ` Martin Schwidefsky
2018-02-28 22:31 ` [PATCH v3 2/4] mm: Split page_type out from _map_count Matthew Wilcox
2018-02-28 22:31 ` Matthew Wilcox [this message]
2018-02-28 22:31 ` [PATCH v3 4/4] mm: Mark pages in use for page tables Matthew Wilcox
2018-02-28 23:22 ` [PATCH v3 0/4] Split page_type out from mapcount Randy Dunlap
2018-03-01 1:31 ` Matthew Wilcox
2018-03-01 7:17 ` Martin Schwidefsky
2018-03-01 8:00 ` Martin Schwidefsky
2018-03-01 12:44 ` Kirill A. Shutemov
2018-03-01 14:47 ` Martin Schwidefsky
2018-03-01 14:50 ` Matthew Wilcox
2018-03-01 15:02 ` Martin Schwidefsky
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=20180228223157.9281-4-willy@infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).