[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190816101401.32382-1-vbabka@suse.cz>
Date: Fri, 16 Aug 2019 12:13:58 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Michal Hocko <mhocko@...nel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Matthew Wilcox <willy@...radead.org>,
Vlastimil Babka <vbabka@...e.cz>
Subject: [PATCH 0/3] debug_pagealloc improvements through page_owner
The debug_pagealloc functionality serves a similar purpose on the page
allocator level that slub_debug does on the kmalloc level, which is to detect
bad users. One notable feature that slub_debug has is storing stack traces of
who last allocated and freed the object. On page level we track allocations via
page_owner, but that info is discarded when freeing, and we don't track freeing
at all. This series improves those aspects. With both debug_pagealloc and
page_owner enabled, we can then get bug reports such as the example in Patch 3.
SLUB debug tracking additionaly stores cpu, pid and timestamp. This could be
added later, if deemed useful enough to justify the additional page_ext
structure size.
Vlastimil Babka (3):
mm, page_owner: record page owner for each subpage
mm, page_owner: keep owner info when freeing the page
mm, page_owner, debug_pagealloc: save and dump freeing stack trace
.../admin-guide/kernel-parameters.txt | 2 +
include/linux/page_ext.h | 1 +
mm/Kconfig.debug | 4 +-
mm/page_owner.c | 123 +++++++++++++-----
4 files changed, 96 insertions(+), 34 deletions(-)
--
2.22.0
Powered by blists - more mailing lists