From: Zishun Yi <vulab@iscas.ac.cn>
To: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: alex@ghiti.fr, kees@kernel.org, charlie@rivosinc.com,
Zishun Yi <vulab@iscas.ac.cn>
Subject: [PATCH v2] riscv: Check the return value of reloc handlers
Date: Sat, 9 May 2026 15:40:46 +0800 [thread overview]
Message-ID: <20260509074046.1747927-1-vulab@iscas.ac.cn> (raw)
Currently, process_accumulated_relocations() ignores the return values
from both reloc_handler() and accumulate_handler().
As a result, the kernel will proceed to load the module with corrupted
or incomplete sections, which can lead to unpredictable behavior or
kernel panics.
So we need to check the return values of the handlers to propagate the
error, and fall back to the cleanup mode.
Fixes: 8fd6c5142395 ("riscv: Add remaining module relocations")
Assisted-by: Gemini:gemini-3.1-pro
Signed-off-by: Zishun Yi <vulab@iscas.ac.cn>
---
Changes in v2:
- Added 'Assisted-by' tag.
arch/riscv/kernel/module.c | 24 ++++++++++++++++--------
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/arch/riscv/kernel/module.c b/arch/riscv/kernel/module.c
index 1961135689db..b6512fa9aca1 100644
--- a/arch/riscv/kernel/module.c
+++ b/arch/riscv/kernel/module.c
@@ -594,7 +594,7 @@ static const struct relocation_handlers reloc_handlers[] = {
/* 192-255 nonstandard ABI extensions */
};
-static void
+static int
process_accumulated_relocations(struct module *me,
struct hlist_head **relocation_hashtable,
struct list_head *used_buckets_list)
@@ -625,6 +625,7 @@ process_accumulated_relocations(struct module *me,
int curr_type;
void *location;
long buffer;
+ int res, error = 0;
list_for_each_entry_safe(bucket_iter, bucket_iter_tmp,
used_buckets_list, head) {
@@ -637,18 +638,27 @@ process_accumulated_relocations(struct module *me,
&rel_head_iter->rel_entry,
head) {
curr_type = rel_entry_iter->type;
- reloc_handlers[curr_type].reloc_handler(
- me, &buffer, rel_entry_iter->value);
+ if (!error) {
+ res = reloc_handlers[curr_type].reloc_handler(
+ me, &buffer, rel_entry_iter->value);
+ if (res)
+ error = res;
+ }
kfree(rel_entry_iter);
}
- reloc_handlers[curr_type].accumulate_handler(
- me, location, buffer);
+ if (!error) {
+ res = reloc_handlers[curr_type].accumulate_handler(
+ me, location, buffer);
+ if (res)
+ error = res;
+ }
kfree(rel_head_iter);
}
kfree(bucket_iter);
}
kvfree(*relocation_hashtable);
+ return error;
}
static int add_relocation_to_accumulate(struct module *me, int type,
@@ -886,10 +896,8 @@ int apply_relocate_add(Elf_Shdr *sechdrs, const char *strtab,
return res;
}
- process_accumulated_relocations(me, &relocation_hashtable,
+ return process_accumulated_relocations(me, &relocation_hashtable,
&used_buckets_list);
-
- return 0;
}
int module_finalize(const Elf_Ehdr *hdr,
--
2.51.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2026-05-09 7:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260509074046.1747927-1-vulab@iscas.ac.cn \
--to=vulab@iscas.ac.cn \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@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