From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel@sholland.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
heiko@sntech.de, aou@eecs.berkeley.edu,
alexandre.ghiti@canonical.com, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] riscv: Fix crash during early errata patching
Date: Fri, 09 Dec 2022 19:00:16 +0000 [thread overview]
Message-ID: <167061241627.2369.16766839910285576298.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221126060920.65009-1-samuel@sholland.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sat, 26 Nov 2022 00:09:19 -0600 you wrote:
> The patch function for the T-Head PBMT errata calls __pa_symbol() before
> relocation. This crashes when CONFIG_DEBUG_VIRTUAL is enabled, because
> __pa_symbol() forwards to __phys_addr_symbol(), and __phys_addr_symbol()
> checks against the absolute kernel start/end address.
>
> Fix this by checking against the kernel map instead of a symbol address.
>
> [...]
Here is the summary with links:
- [v2,1/2] riscv: Fix crash during early errata patching
https://git.kernel.org/riscv/c/61b2f0bdaa3c
- [v2,2/2] riscv: Move cast inside kernel_mapping_[pv]a_to_[vp]a
https://git.kernel.org/riscv/c/583286e2072e
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-12-09 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 6:09 [PATCH v2 1/2] riscv: Fix crash during early errata patching Samuel Holland
2022-11-26 6:09 ` [PATCH v2 2/2] riscv: Move cast inside kernel_mapping_[pv]a_to_[vp]a Samuel Holland
2022-12-09 19:00 ` 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=167061241627.2369.16766839910285576298.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexandre.ghiti@canonical.com \
--cc=aou@eecs.berkeley.edu \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel@sholland.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