From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, heiko@sntech.de,
bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
jmontleo@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH -fixes] riscv: Do not use fortify in early code
Date: Thu, 17 Oct 2024 16:30:37 +0000 [thread overview]
Message-ID: <172918263750.2528145.8683172772221919308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241009072749.45006-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 9 Oct 2024 09:27:49 +0200 you wrote:
> Early code designates the code executed when the MMU is not yet enabled,
> and this comes with some limitations (see
> Documentation/arch/riscv/boot.rst, section "Pre-MMU execution").
>
> FORTIFY_SOURCE must be disabled then since it can trigger kernel panics
> as reported in [1].
>
> [...]
Here is the summary with links:
- [-fixes] riscv: Do not use fortify in early code
https://git.kernel.org/riscv/c/d49320974c4e
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:[~2024-10-17 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 7:27 [PATCH -fixes] riscv: Do not use fortify in early code Alexandre Ghiti
2024-10-15 20:05 ` Felix Yan
2024-10-15 22:04 ` Jessica Clarke
2024-10-16 5:26 ` Jason Montleon
2024-10-16 11:26 ` Alexandre Ghiti
2024-10-16 15:30 ` Jessica Clarke
2024-10-16 16:56 ` Kees Cook
2024-10-17 16:30 ` 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=172918263750.2528145.8683172772221919308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=heiko@sntech.de \
--cc=jmontleo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox