From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: [PATCH 0/3][RFC] mm/page:_owner: track page free call chain
Date: Sun, 3 Jul 2016 01:16:53 +0900 [thread overview]
Message-ID: <20160702161656.14071-1-sergey.senozhatsky@gmail.com> (raw)
Hello,
RFC
Page owner tracks a call chain that has allocated a page, this
patch set extends it with a PAGE_OWNER_TRACK_FREE functionality,
that now also tracks a call chain that has freed the page.
Page dump, thus, now has the following format:
a) page allocated backtrace
b) page free backtrace
c) backtrace of path that has trigger bad page
For a quick example of a case when this new b) part can make a
difference please see 0003.
Sergey Senozhatsky (3):
mm/page_owner: rename page_owner functions
mm/page_owner: rename PAGE_EXT_OWNER flag
mm/page_owner: track page free call chain
include/linux/page_ext.h | 15 ++++++-
include/linux/page_owner.h | 16 +++----
lib/Kconfig.debug | 10 +++++
mm/page_alloc.c | 4 +-
mm/page_owner.c | 110 +++++++++++++++++++++++++++++++--------------
mm/vmstat.c | 5 ++-
6 files changed, 113 insertions(+), 47 deletions(-)
--
2.9.0.37.g6d523a3
--
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 reply other threads:[~2016-07-02 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 16:16 Sergey Senozhatsky [this message]
2016-07-02 16:16 ` [PATCH 1/3] mm/page_owner: rename page_owner functions Sergey Senozhatsky
2016-07-02 16:16 ` [PATCH 2/3] mm/page_owner: rename PAGE_EXT_OWNER flag Sergey Senozhatsky
2016-07-02 16:16 ` [PATCH 3/3] mm/page_owner: track page free call chain Sergey Senozhatsky
2016-07-03 5:59 ` Sergey Senozhatsky
2016-07-04 4:57 ` Joonsoo Kim
2016-07-04 5:07 ` Sergey Senozhatsky
2016-07-04 5:29 ` Joonsoo Kim
2016-07-04 5:45 ` Sergey Senozhatsky
2016-07-04 7:29 ` Joonsoo Kim
2016-07-04 7:53 ` Sergey Senozhatsky
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=20160702161656.14071-1-sergey.senozhatsky@gmail.com \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=vbabka@suse.cz \
/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