From: Markus Elfring <Markus.Elfring@web.de>
To: vulab@iscas.ac.cn, linux-riscv@lists.infradead.org,
Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <pjw@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, Alexandre Ghiti <alex@ghiti.fr>,
Kees Cook <kees@kernel.org>, Maxim Kochetkov <fido_max@inbox.ru>,
Samuel Holland <samuel.holland@sifive.com>,
Will Pierce <wgpierce17@gmail.com>
Subject: Re: [PATCH] riscv: Check the return value of reloc handlers
Date: Sun, 22 Mar 2026 08:26:49 +0100 [thread overview]
Message-ID: <af317acf-cfe4-4e85-a0cc-e99d67c233c5@web.de> (raw)
In-Reply-To: <20260321113419.34437-1-vulab@iscas.ac.cn>
> Currently, process_accumulated_relocations() ignores the return values
> from both reloc_handler() and accumulate_handler().
Were any source code analysis tools involved here?
…
> So we need to check the return values of the handlers to propagate the
> error, and fall back to the cleanup mode.
See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.0-rc4#n94
> Fixes: 8fd6c5142395 ("riscv: Add remaining module relocations")
See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.0-rc4#n34
> Signed-off-by: Zishun Yi <vulab@iscas.ac.cn>
Do multiple personal names fit really to the same email address according to
the Developer's Certificate of Origin?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.0-rc4#n396
Were code review results presented from an “university laboratory” so far?
https://github.com/ISCAS-Vulab/
https://english.is.cas.cn/
Regards,
Markus
parent reply other threads:[~2026-03-22 7:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260321113419.34437-1-vulab@iscas.ac.cn>]
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=af317acf-cfe4-4e85-a0cc-e99d67c233c5@web.de \
--to=markus.elfring@web.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=fido_max@inbox.ru \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=vulab@iscas.ac.cn \
--cc=wgpierce17@gmail.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