https://sourceware.org/bugzilla/show_bug.cgi?id=34809
Bug ID: 34809
Summary: GNU ld LoongArch TLS relocation families dereference
an absent GOT
Product: binutils
Version: 2.46
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: basavesh.shivakumar at wsu dot edu
Target Milestone: ---
Created attachment 17129
--> https://sourceware.org/bugzilla/attachment.cgi?id=17129&action=edit
repro
I'm reporting this bug on behalf of my team: Ananta Srikar Puranam, Emily West,
Dr. Swarn Priya, Dr. Peng Gao and Dr. Basavesh Ammanaghatta Shivakumar.
Summary
=======
Matching-backend, assembler-produced LoongArch TLS relocations reach final
relocation without required GOT state: standalone R_LARCH_TLS_GD_PCREL20_S2,
orphan R_LARCH_TLS_DESC_PC_LO12, and orphan R_LARCH_TLS_IE64_PC_LO20 read
through the NULL .got section at current source lines 4804, 4843, and 4875; GNU
ld 2.46 crashes on all three while complete TLSDESC and IE-with-HI20 controls
pass.
Reproduction
============
1. Download and extract
`bfd-loongarch-tls-relocation-missing-got-null-dereference-reproducer.tar.gz`.
2. Run the following command with an ld.bfd or all-target `ld-new` binary that
supports the emulation used by the reproducer:
LD_BFD=/path/to/ld-new sh repro.sh
The archive contains the fixed input files, independent controls, helper
scripts needed by `repro.sh`, and their checksums. The script uses a temporary
directory and does not modify the source tree.
Observed result
===============
Matching-backend, assembler-produced LoongArch TLS relocations reach final
relocation without required GOT state: standalone R_LARCH_TLS_GD_PCREL20_S2,
orphan R_LARCH_TLS_DESC_PC_LO12, and orphan R_LARCH_TLS_IE64_PC_LO20 read
through the NULL .got section at current source lines 4804, 4843, and 4875; GNU
ld 2.46 crashes on all three while complete TLSDESC and IE-with-HI20 controls
pass.
Expected result
===============
GNU ld should either produce the correct output or reject the input with a
normal diagnostic. It should not crash, hang, execute undefined behavior, read
outside an input-derived allocation, or produce the described malformed
output.
--
You are receiving this mail because:
You are on the CC list for the bug.
