From: Petr Tesarik <petrtesarik@huaweicloud.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor.dooley@microchip.com>,
Li Huafei <lihuafei1@huawei.com>,
Liao Chang <liaochang1@huawei.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Stuebner <heiko@sntech.de>,
Ricardo Ribalda <ribalda@chromium.org>,
Alyssa Ross <hi@alyssa.is>, Li Zhengyu <lizhengyu3@huawei.com>,
linux-riscv@lists.infradead.org (open list:RISC-V ARCHITECTURE),
kexec@lists.infradead.org,
linux-kernel@vger.kernel.org (open list)
Cc: Torsten Duwe <duwe@suse.de>,
Roberto Sassu <roberto.sassu@huaweicloud.com>,
petr@tesarici.cz
Subject: [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures
Date: Wed, 26 Jul 2023 11:53:58 +0200 [thread overview]
Message-ID: <cover.1690365011.git.petr.tesarik.ext@huawei.com> (raw)
From: Petr Tesarik <petr.tesarik.ext@huawei.com>
The kexec_file_load(2) syscall does not work at least in some kernel
builds. For details see the relevant section in this blog post:
https://sigillatum.tesarici.cz/2023-07-21-state-of-riscv64-kdump.html
This patch series handles an additional relocation types, removes the need
to implement a Global Offset Table (GOT) for the purgatory and fixes the
placement of initrd.
Changelog
=========
Changes from v1:
- Replace memcmp() with a for loop.
- Drop handling of 16-bit add/subtract relocations. They were used only
by alternatives in strcmp(), which was referenced only by string.o.
- Add the initrd placement fix.
Petr Tesarik (1):
riscv/purgatory: do not link with string.o and its dependencies
Torsten Duwe (2):
riscv/kexec: handle R_RISCV_CALL_PLT relocation type
riscv/kexec: load initrd high in available memory
arch/riscv/kernel/elf_kexec.c | 3 ++-
arch/riscv/purgatory/Makefile | 26 +-------------------------
arch/riscv/purgatory/purgatory.c | 6 ++++--
3 files changed, 7 insertions(+), 28 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-26 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 9:53 Petr Tesarik [this message]
2023-07-26 9:53 ` [PATCH v2 1/3] riscv/kexec: handle R_RISCV_CALL_PLT relocation type Petr Tesarik
2023-07-26 16:30 ` Conor Dooley
2023-07-26 9:54 ` [PATCH v2 2/3] riscv/purgatory: do not link with string.o and its dependencies Petr Tesarik
2023-07-26 16:33 ` Conor Dooley
2023-08-03 15:13 ` Palmer Dabbelt
2023-08-03 15:17 ` Conor Dooley
2023-08-03 15:33 ` Petr Tesarik
2023-07-26 9:54 ` [PATCH v2 3/3] riscv/kexec: load initrd high in available memory Petr Tesarik
2023-07-26 16:38 ` Conor Dooley
2023-07-26 18:27 ` Petr Tesarik
2023-08-01 9:27 ` [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures Petr Tesarik
2023-08-03 15:10 ` patchwork-bot+linux-riscv
2023-08-09 14:35 ` (subset) " Palmer Dabbelt
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=cover.1690365011.git.petr.tesarik.ext@huawei.com \
--to=petrtesarik@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=duwe@suse.de \
--cc=heiko@sntech.de \
--cc=hi@alyssa.is \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=liaochang1@huawei.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=masahiroy@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=petr@tesarici.cz \
--cc=ribalda@chromium.org \
--cc=roberto.sassu@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).