From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, Qian Cai <cai@lca.pw>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dmitry Vyukov <dvyukov@google.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Walter Wu <walter-zh.wu@mediatek.com>
Subject: [PATCH v2 0/3] followups to debug_pagealloc improvements through page_owner
Date: Mon, 30 Sep 2019 14:29:13 +0200 [thread overview]
Message-ID: <20190930122916.14969-1-vbabka@suse.cz> (raw)
Changes since v1 [3]:
- Kirill suggested further decoupling of freeing stack capture from KASAN and
debug_pagealloc. Also the stackdepot handle is now only allocated in page_ext
when actually used (it was simpler than I initially thought). As that was a
large change, I've dropped Reviewed-by from Andrey Ryabinin.
- More minor changes suggested by Kirill.
These are followups to [1] which made it to Linus meanwhile. Patches 1 and 3
are based on Kirill's review, patch 2 on KASAN request [2]. It would be nice
if all of this made it to 5.4 with [1] already there (or at least Patch 1).
[1] https://lore.kernel.org/linux-mm/20190820131828.22684-1-vbabka@suse.cz/
[2] https://lore.kernel.org/linux-arm-kernel/20190911083921.4158-1-walter-zh.wu@mediatek.com/
[3] https://lore.kernel.org/r/20190925143056.25853-1-vbabka%40suse.cz
Vlastimil Babka (3):
mm, page_owner: fix off-by-one error in __set_page_owner_handle()
mm, page_owner: decouple freeing stack trace from debug_pagealloc
mm, page_owner: rename flag indicating that page is allocated
.../admin-guide/kernel-parameters.txt | 8 ++
Documentation/dev-tools/kasan.rst | 3 +
include/linux/page_ext.h | 10 +-
include/linux/page_owner.h | 1 +
mm/page_ext.c | 24 ++--
mm/page_owner.c | 117 ++++++++++++------
6 files changed, 109 insertions(+), 54 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-30 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 12:29 Vlastimil Babka [this message]
2019-09-30 12:29 ` [PATCH v2 1/3] mm, page_owner: fix off-by-one error in __set_page_owner_handle() Vlastimil Babka
2019-09-30 12:29 ` [PATCH v2 2/3] mm, page_owner: decouple freeing stack trace from debug_pagealloc Vlastimil Babka
2019-09-30 12:49 ` Qian Cai
2019-09-30 21:39 ` Vlastimil Babka
2019-09-30 23:49 ` Qian Cai
2019-10-01 8:07 ` Vlastimil Babka
2019-10-01 11:51 ` Kirill A. Shutemov
2019-10-01 12:26 ` Qian Cai
2019-10-01 12:31 ` Kirill A. Shutemov
2019-10-01 12:32 ` Vlastimil Babka
2019-10-01 12:35 ` Vlastimil Babka
2019-10-01 13:18 ` Qian Cai
2019-10-01 14:15 ` Vlastimil Babka
2019-10-01 11:35 ` Kirill A. Shutemov
2019-09-30 12:29 ` [PATCH v2 3/3] mm, page_owner: rename flag indicating that page is allocated Vlastimil Babka
2019-09-30 12:49 ` Vlastimil Babka
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=20190930122916.14969-1-vbabka@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=walter-zh.wu@mediatek.com \
--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).