From: Charlie Jenkins <charlie@rivosinc.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v4 0/2] riscv: Add remaining module relocations and tests
Date: Wed, 18 Oct 2023 10:31:29 -0700 [thread overview]
Message-ID: <ZTAWcX1qVhkC71BJ@ghost> (raw)
In-Reply-To: <20231018-smite-bungee-f46b15b4ce6f@spud>
On Wed, Oct 18, 2023 at 12:35:55PM +0100, Conor Dooley wrote:
> Hey Charlie,
>
> On Tue, Oct 17, 2023 at 10:34:15PM -0700, Charlie Jenkins wrote:
> > A handful of module relocations were missing, this patch includes the
> > remaining ones. I also wrote some test cases to ensure that module
> > loading works properly. Some relocations cannot be supported in the
> > kernel, these include the ones that rely on thread local storage and
> > dynamic linking.
> >
> > ULEB128 handling is a bit special because SET and SUB relocations must
> > happen together, and SET must happen before SUB. A psABI proposal [1]
> > mandates that the first SET_ULEB128 that appears before a SUB_ULEB128
> > is the associated SET_ULEB128.
> >
> > This can be tested by enabling KUNIT, RUNTIME_KERNEL_TESTING_MENU, and
> > RISCV_MODULE_LINKING_KUNIT.
> >
> > [1] https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/403
> >
> > Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> > ---
> > Changes in v4:
> > - Complete removal of R_RISCV_RVC_LUI
> > - Fix bug in R_RISCV_SUB6 linking
> > - Only build ULEB128 tests if supported by toolchain
> > - Link to v3: https://lore.kernel.org/r/20231016-module_relocations-v3-0-a667fd6071e9@rivosinc.com
>
> On patch 2/2:
>
> ../arch/riscv/kernel/tests/module_test/test_uleb128.S:18:17: error: unknown relocation name
> ../arch/riscv/kernel/tests/module_test/test_uleb128.S:19:17: error: unknown relocation name
>
> Same toolchain configuration in the patchwork automation as before.
>
> Cheers,
> Conor.
Where do you see this error? On Patchwork I see a success [1].
[1] https://patchwork.kernel.org/project/linux-riscv/patch/20231017-module_relocations-v4-2-937f5ef316f0@rivosinc.com/
>
> >
> > Changes in v3:
> > - Add prototypes to test_module_linking_main as recommended by intel
> > zero day bot
> > - Improve efficiency of ULEB128 pair matching
> > - Link to v2: https://lore.kernel.org/r/20231006-module_relocations-v2-0-47566453fedc@rivosinc.com
> >
> > Changes in v2:
> > - Added ULEB128 relocations
> > - Link to v1: https://lore.kernel.org/r/20230913-module_relocations-v1-0-bb3d8467e793@rivosinc.com
> >
> > ---
> > Charlie Jenkins (2):
> > riscv: Add remaining module relocations
> > riscv: Add tests for riscv module loading
> >
> > arch/riscv/Kconfig.debug | 1 +
> > arch/riscv/include/uapi/asm/elf.h | 5 +-
> > arch/riscv/kernel/Makefile | 1 +
> > arch/riscv/kernel/module.c | 207 ++++++++++++++++++---
> > arch/riscv/kernel/tests/Kconfig.debug | 35 ++++
> > arch/riscv/kernel/tests/Makefile | 1 +
> > arch/riscv/kernel/tests/module_test/Makefile | 15 ++
> > .../tests/module_test/test_module_linking_main.c | 85 +++++++++
> > arch/riscv/kernel/tests/module_test/test_set16.S | 23 +++
> > arch/riscv/kernel/tests/module_test/test_set32.S | 20 ++
> > arch/riscv/kernel/tests/module_test/test_set6.S | 23 +++
> > arch/riscv/kernel/tests/module_test/test_set8.S | 23 +++
> > arch/riscv/kernel/tests/module_test/test_sub16.S | 22 +++
> > arch/riscv/kernel/tests/module_test/test_sub32.S | 22 +++
> > arch/riscv/kernel/tests/module_test/test_sub6.S | 22 +++
> > arch/riscv/kernel/tests/module_test/test_sub64.S | 27 +++
> > arch/riscv/kernel/tests/module_test/test_sub8.S | 22 +++
> > arch/riscv/kernel/tests/module_test/test_uleb128.S | 20 ++
> > 18 files changed, 548 insertions(+), 26 deletions(-)
> > ---
> > base-commit: 4d320c2d9a2b22f53523a1b012cda17a50220965
> > change-id: 20230908-module_relocations-f63ced651bd7
> > --
> > - Charlie
> >
next prev parent reply other threads:[~2023-10-18 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 5:34 Charlie Jenkins
2023-10-18 5:34 ` [PATCH v4 1/2] riscv: Add remaining module relocations Charlie Jenkins
2023-10-18 12:17 ` Emil Renner Berthing
2023-10-18 18:31 ` Charlie Jenkins
2023-10-18 18:38 ` Emil Renner Berthing
2023-10-18 20:19 ` Charlie Jenkins
2023-10-18 20:28 ` Emil Renner Berthing
2023-10-18 18:28 ` Samuel Holland
2023-10-18 22:19 ` Charlie Jenkins
2023-10-18 18:47 ` Andreas Schwab
2023-10-18 22:19 ` Charlie Jenkins
2023-10-18 5:34 ` [PATCH v4 2/2] riscv: Add tests for riscv module loading Charlie Jenkins
2023-10-18 11:35 ` [PATCH v4 0/2] riscv: Add remaining module relocations and tests Conor Dooley
2023-10-18 17:31 ` Charlie Jenkins [this message]
2023-10-18 17:41 ` Conor Dooley
2023-10-19 5:56 ` Björn Töpel
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=ZTAWcX1qVhkC71BJ@ghost \
--to=charlie@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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