From: Cyrill Gorcunov <gorcunov@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
linux-mm@kvack.org, Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [BUG -tip] kmemleak and stacktrace cause page faul
Date: Tue, 22 Oct 2019 17:56:19 +0300 [thread overview]
Message-ID: <20191022145619.GE12121@uranus.lan> (raw)
In-Reply-To: <20191022142325.GD12121@uranus.lan>
On Tue, Oct 22, 2019 at 05:23:25PM +0300, Cyrill Gorcunov wrote:
>
> I presume the kmemleak tries to save stack trace too early when estack_pages are not
> yet filled.
Indeed, at this stage of boot the percpu_setup_exception_stacks has not been called
yet and estack_pages full of crap
[ 0.157502] stk 0x1008 k 1 begin 0x0 end 0xd000 estack_pages 0xffffffff82014880 ep 0xffffffff82014888
[ 0.159395] estack_pages[0] = 0x0
[ 0.160046] estack_pages[1] = 0x5100000001000
[ 0.160881] estack_pages[2] = 0x0
[ 0.161530] estack_pages[3] = 0x6100000003000
[ 0.162343] estack_pages[4] = 0x0
[ 0.162962] estack_pages[5] = 0x0
[ 0.163523] estack_pages[6] = 0x0
[ 0.164065] estack_pages[7] = 0x8100000007000
[ 0.164978] estack_pages[8] = 0x0
[ 0.165624] estack_pages[9] = 0x9100000009000
[ 0.166448] estack_pages[10] = 0x0
[ 0.167064] estack_pages[11] = 0xa10000000b000
[ 0.168055] estack_pages[12] = 0x0
[ 0.168891] BUG: unable to handle page fault for address: 0000000000001ff0
next prev parent reply other threads:[~2019-10-22 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 11:44 [BUG -tip] kmemleak and stacktrace cause page faul Cyrill Gorcunov
2019-10-22 14:23 ` Cyrill Gorcunov
2019-10-22 14:56 ` Cyrill Gorcunov [this message]
2019-10-23 13:21 ` Thomas Gleixner
2019-10-23 13:32 ` Cyrill Gorcunov
2019-10-23 13:38 ` Thomas Gleixner
2019-10-23 13:44 ` Cyrill Gorcunov
2019-10-23 13:47 ` Thomas Gleixner
2019-10-23 13:53 ` Cyrill Gorcunov
2019-10-23 13:59 ` Cyrill Gorcunov
2019-10-23 18:05 ` [PATCH] x86/dumpstack/64: Don't evaluate exception stacks before setup Thomas Gleixner
2019-10-23 18:31 ` Matthew Wilcox
2019-10-23 18:43 ` Cyrill Gorcunov
2019-10-23 21:27 ` Thomas Gleixner
2019-10-23 19:17 ` Josh Poimboeuf
2019-11-04 23:56 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
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=20191022145619.GE12121@uranus.lan \
--to=gorcunov@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.