From: Chen Jun <chenjun102@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Cc: <akpm@linux-foundation.org>, <catalin.marinas@arm.com>,
<will@kernel.org>, <rui.xiang@huawei.com>
Subject: [PATCH 0/2] Fix page_owner broken on arm64
Date: Wed, 17 Mar 2021 14:20:48 +0000 [thread overview]
Message-ID: <20210317142050.57712-1-chenjun102@huawei.com> (raw)
On arm64, cat /sys/kernel/debug/page_owner
All pages return the same stack
stack_trace_save+0x4c/0x78
register_early_stack+0x34/0x70
init_page_owner+0x34/0x230
page_ext_init+0x1bc/0x1dc
The reason is arch_stack_walk save 2 more entries than before.
To fix it, add skip in arch_stack_walk
*** BLURB HERE ***
1. Prepare for 2, move stacktrace_cookie to .h
2. Fix the problem
Chen Jun (2):
stacktrace: Move struct stacktrace_cookie to stacktrace.h
arm64: stacktrace: Add skip when task == current
arch/arm64/kernel/stacktrace.c | 5 +++--
include/linux/stacktrace.h | 7 +++++++
kernel/stacktrace.c | 7 -------
3 files changed, 10 insertions(+), 9 deletions(-)
--
2.9.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Chen Jun <chenjun102@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Cc: <akpm@linux-foundation.org>, <catalin.marinas@arm.com>,
<will@kernel.org>, <rui.xiang@huawei.com>
Subject: [PATCH 0/2] Fix page_owner broken on arm64
Date: Wed, 17 Mar 2021 14:20:48 +0000 [thread overview]
Message-ID: <20210317142050.57712-1-chenjun102@huawei.com> (raw)
On arm64, cat /sys/kernel/debug/page_owner
All pages return the same stack
stack_trace_save+0x4c/0x78
register_early_stack+0x34/0x70
init_page_owner+0x34/0x230
page_ext_init+0x1bc/0x1dc
The reason is arch_stack_walk save 2 more entries than before.
To fix it, add skip in arch_stack_walk
*** BLURB HERE ***
1. Prepare for 2, move stacktrace_cookie to .h
2. Fix the problem
Chen Jun (2):
stacktrace: Move struct stacktrace_cookie to stacktrace.h
arm64: stacktrace: Add skip when task == current
arch/arm64/kernel/stacktrace.c | 5 +++--
include/linux/stacktrace.h | 7 +++++++
kernel/stacktrace.c | 7 -------
3 files changed, 10 insertions(+), 9 deletions(-)
--
2.9.4
next reply other threads:[~2021-03-17 14:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 14:20 Chen Jun [this message]
2021-03-17 14:20 ` [PATCH 0/2] Fix page_owner broken on arm64 Chen Jun
2021-03-17 14:20 ` [PATCH 1/2] stacktrace: Move struct stacktrace_cookie to stacktrace.h Chen Jun
2021-03-17 14:20 ` Chen Jun
2021-03-17 14:20 ` [PATCH 2/2] arm64: stacktrace: Add skip when task == current Chen Jun
2021-03-17 14:20 ` Chen Jun
2021-03-17 18:36 ` Catalin Marinas
2021-03-17 18:36 ` Catalin Marinas
2021-03-17 19:34 ` Mark Rutland
2021-03-17 19:34 ` Mark Rutland
2021-03-18 3:24 ` chenjun (AM)
2021-03-18 3:24 ` chenjun (AM)
2021-03-18 13:22 ` chenjun (AM)
2021-03-18 13:22 ` chenjun (AM)
2021-03-18 16:17 ` Catalin Marinas
2021-03-18 16:17 ` Catalin Marinas
2021-03-18 17:12 ` Mark Rutland
2021-03-18 17:12 ` Mark Rutland
2021-03-18 18:36 ` Catalin Marinas
2021-03-18 18:36 ` Catalin Marinas
2021-03-17 22:23 ` [PATCH 0/2] Fix page_owner broken on arm64 Andrew Morton
2021-03-17 22:23 ` Andrew Morton
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=20210317142050.57712-1-chenjun102@huawei.com \
--to=chenjun102@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.xiang@huawei.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.