From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: mcgrof@kernel.org, rdunlap@infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module: Ignore RISC-V mapping symbols too
Date: Fri, 7 Jul 2023 08:06:19 +0200 [thread overview]
Message-ID: <3e905882-7f96-4fc0-aecf-6054ed00372e@t-8ch.de> (raw)
In-Reply-To: <20230707054007.32591-1-palmer@rivosinc.com>
On 2023-07-06 22:40:01-0700, Palmer Dabbelt wrote:
> RISC-V has an extended form of mapping symbols that we use to encode
> the ISA when it changes in the middle of an ELF. This trips up modpost
> as a build failure, I haven't yet verified it yet but I believe the
> kallsyms difference should result in stacks looking sane again.
> [..]
> diff --git a/kernel/module/kallsyms.c b/kernel/module/kallsyms.c
> index ef73ae7c8909..1e988e542c5d 100644
> --- a/kernel/module/kallsyms.c
> +++ b/kernel/module/kallsyms.c
> @@ -12,6 +12,12 @@
> #include <linux/bsearch.h>
> #include "internal.h"
>
> +#ifdef CONFIG_RISCV
> +#define IS_RISCV 1
> +#else
> +#define IS_RISCV 0
> +#endif
> +
> /* Lookup exported symbol in given range of kernel_symbols */
> static const struct kernel_symbol *lookup_exported_symbol(const char *name,
> const struct kernel_symbol *start,
> @@ -289,7 +295,7 @@ static const char *find_kallsyms_symbol(struct module *mod,
> * and inserted at a whim.
> */
> if (*kallsyms_symbol_name(kallsyms, i) == '\0' ||
> - is_mapping_symbol(kallsyms_symbol_name(kallsyms, i)))
> + is_mapping_symbol(kallsyms_symbol_name(kallsyms, i), IS_RISCV))
IS_BUILTIN(CONFIG_RISCV) or IS_ENABLED(CONFIG_RISCV) ?
> continue;
>
> if (thisval <= addr && thisval > bestval) {
> [..]
next prev parent reply other threads:[~2023-07-07 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 5:40 Palmer Dabbelt
2023-07-07 6:06 ` Thomas Weißschuh [this message]
2023-07-07 16:03 ` Palmer Dabbelt
2023-07-07 15:08 ` Randy Dunlap
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=3e905882-7f96-4fc0-aecf-6054ed00372e@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=palmer@rivosinc.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®