mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>, <kbuild-all@lists.01.org>,
	<llvm@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rust:rust-next 2/24] ld.lld: error: kernel/built-in.a(kallsyms.o):(function get_symbol_offset: .text+0x5f0): relocation R_RISCV_PCREL_HI20 out of range: -524435 is not in [-524288, 524287]; references kallsyms_names
Date: Sat, 4 Jun 2022 18:14:27 +0800	[thread overview]
Message-ID: <d4c31c67-de25-ac88-7115-4872e31f8bdf@intel.com> (raw)
In-Reply-To: <CANiq72k69wUZxvCeJFH3=9LsyjT76XFcfbf5aKZbb-u91wMmkQ@mail.gmail.com>

On 6/3/2022 19:01, Miguel Ojeda wrote:
> On Fri, Jun 3, 2022 at 12:32 PM kernel test robot <yujie.liu@intel.com> wrote:
>>
>>   >> ld.lld: error: kernel/built-in.a(kallsyms.o):(function get_symbol_offset: .text+0x5f0): relocation R_RISCV_PCREL_HI20 out of range: -524435 is not in [-524288, 524287]; references kallsyms_names
>>      >>> referenced by kallsyms.c
>>      >>> defined in kernel/built-in.a(kallsyms.o)
> 
> There are similar reports for the same relocation type in trees
> without Rust support merged, so this might not be being triggered by
> Rust itself, e.g.:
> 
>      https://lore.kernel.org/llvm/202206010956.rOpdU4dr-lkp@intel.com/
>      https://lore.kernel.org/llvm/202205280837.PPVZBhXr-lkp@intel.com/

Thanks for the info, it looks like an existing relocation issue in
kallsyms under riscv arch.

commit 2087d6ac3567b (kallsyms: support "big" kernel symbols) changed
some code of kallsyms to support long Rust symbols, so it exposed that
relocation issue and triggered this report.

We'll do more checks next time to ensure the reported issue is indeed
Rust related.

Thanks,
Yujie

> 
> Cheers,
> Miguel

      reply	other threads:[~2022-06-04 10:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202205240321.sb0gX2mq-lkp@intel.com>
2022-06-03 10:32 ` kernel test robot
2022-06-03 11:01   ` Miguel Ojeda
2022-06-04 10:14     ` Yujie Liu [this message]

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=d4c31c67-de25-ac88-7115-4872e31f8bdf@intel.com \
    --to=yujie.liu@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@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

all inboxes | Powered by JetHome®