From: Ard Biesheuvel <ardb@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
speakup@linux-speakup.org, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master] BUILD REGRESSION 543b9b2fe10b2e12b8d773af65314d322f91e479
Date: Mon, 9 Jan 2023 15:38:17 +0100 [thread overview]
Message-ID: <CAMj1kXGAf7ikEU5jLoik0xrOde0xBg0yJkOo5=PtEtNXoUxMXA@mail.gmail.com> (raw)
In-Reply-To: <63bc16ce.IBWX7dhtPEB7dLIq%lkp@intel.com>
On Mon, 9 Jan 2023 at 14:31, kernel test robot <lkp@intel.com> wrote:
>
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 543b9b2fe10b2e12b8d773af65314d322f91e479 Add linux-next specific files for 20230109
>
> Error/Warning: (recently discovered and may have been fixed)
>
> aarch64-linux-ld: ID map text too big or misaligned
This is caused by linker veneers ('stubs') that are emitted into the
ID map text section:
*(.idmap.text)
.idmap.text 0xffffffc018c04000 0x38 arch/arm64/kernel/hyp-stub.o
.idmap.text 0xffffffc018c04038 0x28 arch/arm64/kernel/sleep.o
0xffffffc018c04038 cpu_resume
.idmap.text 0xffffffc018c04060 0x38 arch/arm64/kernel/cpu-reset.o
0xffffffc018c04060 cpu_soft_restart
.idmap.text 0xffffffc018c04098 0x468 arch/arm64/kernel/head.o
0xffffffc018c04098 init_kernel_el
0xffffffc018c04290 secondary_holding_pen
0xffffffc018c042c8 secondary_entry
0xffffffc018c043c4 __enable_mmu
0xffffffc018c0440c __cpu_secondary_check52bitva
.idmap.text 0xffffffc018c04500 0x3c4 arch/arm64/mm/proc.o
0xffffffc018c04500 cpu_do_resume
0xffffffc018c045a8 idmap_cpu_replace_ttbr1
0xffffffc018c045d4 idmap_kpti_install_ng_mappings
0xffffffc018c047bc __cpu_setup
*fill* 0xffffffc018c048c4 0x4
.idmap.text.stub
0xffffffc018c048c8 0xf7c8 linker stubs
0xffffffc018c1c8c8 __idmap_text_end = .
It seems unlikely that the entire .idmap.text.stub section is
dedicated to veneers for code in .idmap.text, and the linker probably
dumps them here because the next output section is non-executable.
I have patches on the list that move the ID map out of the .text
section altogether (among other things) and this seems like a suitable
workaround for this issue as well.
https://lore.kernel.org/all/20221129161418.1968319-3-ardb@kernel.org/
next prev parent reply other threads:[~2023-01-09 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 13:29 kernel test robot
2023-01-09 14:38 ` Ard Biesheuvel [this message]
2023-01-11 10:26 ` Ard Biesheuvel
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='CAMj1kXGAf7ikEU5jLoik0xrOde0xBg0yJkOo5=PtEtNXoUxMXA@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=speakup@linux-speakup.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