From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
daire.mcnamara@microchip.com, anup@brainfault.org,
atishp@rivosinc.com, mick@ics.forth.gr,
linux-kernel@vger.kernel.org,
valentina.fernandezalanis@microchip.com, e.shatokhin@yadro.com
Subject: Re: [PATCH v1] riscv: fix reserved memory setup
Date: Thu, 10 Nov 2022 23:10:14 +0000 [thread overview]
Message-ID: <166812181467.9076.159650897116586866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221107151524.3941467-1-conor.dooley@microchip.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 7 Nov 2022 15:15:25 +0000 you wrote:
> Currently, RISC-V sets up reserved memory using the "early" copy of the
> device tree. As a result, when trying to get a reserved memory region
> using of_reserved_mem_lookup(), the pointer to reserved memory regions
> is using the early, pre-virtual-memory address which causes a kernel
> panic when trying to use the buffer's name:
>
> Unable to handle kernel paging request at virtual address 00000000401c31ac
> Oops [#1]
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 6.0.0-rc1-00001-g0d9d6953d834 #1
> Hardware name: Microchip PolarFire-SoC Icicle Kit (DT)
> epc : string+0x4a/0xea
> ra : vsnprintf+0x1e4/0x336
> epc : ffffffff80335ea0 ra : ffffffff80338936 sp : ffffffff81203be0
> gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000
> t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20
> s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 : 0000000000000000
> a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff
> a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff
> s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 : 0000000000000008
> s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00
> s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002
> s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 : ffffffff812f3617
> t5 : ffffffff812f3618 t6 : ffffffff81203d08
> status: 0000000200000100 badaddr: 00000000401c31ac cause: 000000000000000d
> [<ffffffff80338936>] vsnprintf+0x1e4/0x336
> [<ffffffff80055ae2>] vprintk_store+0xf6/0x344
> [<ffffffff80055d86>] vprintk_emit+0x56/0x192
> [<ffffffff80055ed8>] vprintk_default+0x16/0x1e
> [<ffffffff800563d2>] vprintk+0x72/0x80
> [<ffffffff806813b2>] _printk+0x36/0x50
> [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24
> [<ffffffff808057ec>] paging_init+0x528/0x5bc
> [<ffffffff808031ae>] setup_arch+0xd0/0x592
> [<ffffffff8080070e>] start_kernel+0x82/0x73c
>
> [...]
Here is the summary with links:
- [v1] riscv: fix reserved memory setup
https://git.kernel.org/riscv/c/50e63dd8ed92
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-10 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 15:15 [PATCH v1] riscv: fix reserved memory setup Conor Dooley
2022-11-07 21:40 ` Evgenii Shatokhin
2022-11-08 7:27 ` Conor Dooley
2022-11-10 22:54 ` Palmer Dabbelt
2022-11-10 23:10 ` patchwork-bot+linux-riscv [this message]
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=166812181467.9076.159650897116586866.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=e.shatokhin@yadro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=valentina.fernandezalanis@microchip.com \
/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