https://sourceware.org/bugzilla/show_bug.cgi?id=34841
Bug ID: 34841
Summary: GNU ld PPC64 undefined IFUNC static links dereference
a missing PLT section
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 17161
--> https://sourceware.org/bugzilla/attachment.cgi?id=17161&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
=======
A canonical PPC64 R_PPC64_ADDR64 reference to an undefined global GNU IFUNC
makes static GNU ld size a global entry stub without a PLT output section and
dereference NULL at elf64-ppc.c:10215; current and GNU ld 2.46 plain builds
SIGSEGV, while an ordinary-FUNC type control gives a clean undefined-reference
error.
Reproduction
============
1. Download and extract
`bfd-ppc64-undefined-ifunc-missing-plt-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
===============
A canonical PPC64 R_PPC64_ADDR64 reference to an undefined global GNU IFUNC
makes static GNU ld size a global entry stub without a PLT output section and
dereference NULL at elf64-ppc.c:10215; current and GNU ld 2.46 plain builds
SIGSEGV, while an ordinary-FUNC type control gives a clean undefined-reference
error.
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.
