LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hsin-Yi Wang <hsinyi@chromium.org>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Boyd <swboyd@chromium.org>,
Kees Cook <keescook@chromium.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Architecture Mailman List <boot-architecture@lists.linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Miles Chen <miles.chen@mediatek.com>,
James Morse <james.morse@arm.com>,
Andrew Murray <andrew.murray@arm.com>
Subject: Re: [PATCH v2 2/2] amr64: map FDT as RW for early_init_dt_scan()
Date: Wed, 15 May 2019 18:24:03 +0800 [thread overview]
Message-ID: <CAJMQK-gMa81kHaTS1kwTcOy+Avt5GsmNcagfscdLdmzS31Tobw@mail.gmail.com> (raw)
In-Reply-To: <20190514154223.GA11115@rapoport-lnx>
On Tue, May 14, 2019 at 11:42 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
> I'm not sure if early console is available at the time kaslr_early_init()
> is called, but if yes, running with memblock=debug may shed some light.
>
> > I didn't trace the real reason causing this. But in this case, maybe
> > don't call memblock_reserve() in kaslr?
>
> My concern that this uncovered a real bug which might hit us later.
>
Hi Mike,
Thanks for the hint. I tried on my device but seems that earlycon
happens after the warning call trace, so can't more information.
Since on my device kaslr will be runned, I tried call
memblock_reserve() in kaslr and not in
setup_machine_fdt()#fixmap_remap_fdt, but got following warning
[ 0.000000] memblock_remove:
[0x0001000000000000-0x0000fffffffffffe] arm64_memblock_init+0x28/0x224
[ 0.000000] memblock_remove:
[0x0000004040000000-0x000000403ffffffe] arm64_memblock_init+0x64/0x224
[ 0.000000] memblock_reserve:
[0x0000000040080000-0x00000000413c3fff]
arm64_memblock_init+0x188/0x224
[ 0.000000] WARNING: CPU: 0 PID: 0 at
/mnt/host/source/src/third_party/kernel/v4.19/mm/memblock.c:583
memblock_add_range+0x1bc/0x1c8
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.19.38 #222
[ 0.000000] Hardware name: MediaTek kukui rev2 board (DT)
[ 0.000000] pstate: 60000085 (nZCv daIf -PAN -UAO)
[ 0.000000] pc : memblock_add_range+0x1bc/0x1c8
[ 0.000000] lr : memblock_add_range+0x30/0x1c8
[ 0.000000] sp : ffffffab68603ea0
[ 0.000000] x29: ffffffab68603ef0 x28: 0000000040954324
[ 0.000000] x27: 0000000040080000 x26: 0000000000080000
[ 0.000000] x25: 0000000080127e4b x24: ffffffab68716000
[ 0.000000] x23: ffffffab680b5000 x22: 0000000001344000
[ 0.000000] x21: 0000000040080000 x20: 0000000000000000
[ 0.000000] x19: ffffffab6864bf00 x18: 00000000fffffc94
[ 0.000000] x17: 000000000000003c x16: ffffffab67d49064
[ 0.000000] x15: 0000000000000006 x14: 626d656d5f34366d
[ 0.000000] x13: 7261205d66666633 x12: 0000000000000000
[ 0.000000] x11: 0000000000000000 x10: ffffffffffffffff
[ 0.000000] x9 : 0000000000011547 x8 : ffffffab68765690
[ 0.000000] x7 : 696e695f6b636f6c x6 : ffffffab6875dd41
[ 0.000000] x5 : 0000000000000000 x4 : 0000000000000000
[ 0.000000] x3 : ffffffab678a24a0 x2 : 0000000001344000
[ 0.000000] x1 : 0000000040080000 x0 : ffffffab6864bf00
[ 0.000000] Call trace:
[ 0.000000] memblock_add_range+0x1bc/0x1c8
[ 0.000000] memblock_reserve+0x60/0xac
[ 0.000000] arm64_memblock_init+0x188/0x224
[ 0.000000] setup_arch+0x138/0x19c
[ 0.000000] start_kernel+0x68/0x380
[ 0.000000] random: get_random_bytes called from
print_oops_end_marker+0x3c/0x58 with crng_init=0
[ 0.000000] ---[ end trace ea99802b425f7adf ]---
[ 0.000000] memblock_reserve:
[0x000000005f800000-0x000000005f811536]
early_init_dt_reserve_memory_arch+0x38/0x48
[ 0.000000] memblock_reserve:
[0x00000000ffe00000-0x00000000ffffffff]
early_init_dt_reserve_memory_arch+0x38/0x48
So I guess we just can't call memblock_reserve() in kaslr?
next prev parent reply other threads:[~2019-05-15 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 0:38 [PATCH v2 1/2] fdt: add support for rng-seed Hsin-Yi Wang
2019-05-13 0:38 ` [PATCH v2 2/2] amr64: map FDT as RW for early_init_dt_scan() Hsin-Yi Wang
2019-05-13 8:58 ` Mike Rapoport
2019-05-13 11:14 ` Hsin-Yi Wang
2019-05-14 15:42 ` Mike Rapoport
2019-05-15 10:24 ` Hsin-Yi Wang [this message]
2019-05-15 20:11 ` Ard Biesheuvel
2019-05-16 11:07 ` Mike Rapoport
2019-05-14 21:05 ` Stephen Boyd
2019-05-15 5:00 ` Mike Rapoport
2019-05-15 10:34 ` Hsin-Yi Wang
2019-05-13 8:42 ` [PATCH v2 1/2] fdt: add support for rng-seed Mike Rapoport
2019-05-13 13:14 ` Rob Herring
2019-05-15 9:07 ` Hsin-Yi Wang
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=CAJMQK-gMa81kHaTS1kwTcOy+Avt5GsmNcagfscdLdmzS31Tobw@mail.gmail.com \
--to=hsinyi@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.murray@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=boot-architecture@lists.linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=miles.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=swboyd@chromium.org \
--cc=will.deacon@arm.com \
--subject='Re: [PATCH v2 2/2] amr64: map FDT as RW for early_init_dt_scan()' \
/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
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).