Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
_binutils_ linker no longer terminates unexpectedly when encountering relocations against absolute address
Previously, the linker from the _binutils_ package could not properly handle relocations against an absolute address. As a consequence, encountering such relocations caused a segmentation fault of the linker.
The linker has been extended to handle relocations against absolute addresses and the problem no longer occurs.
DescriptionChristine Caulfield
2018-03-16 13:11:14 UTC
Description of problem:
When compiling the latest corosync on RHEL7.4 it crashes at link time with
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped
Version-Release number of selected component (if applicable):
binutils-2.27-27.base.el7.x86_64
libgcc-4.8.5-28.el7.x86_64
gcc-c++-4.8.5-28.el7.x86_64
gccxml-0.9.0-0.27.20150423.git3afa8ba.el7.x86_64
gcc-4.8.5-28.el7.x86_64
gcc-gfortran-4.8.5-28.el7.x86_64
glibc-devel-2.17-222.el7.x86_64
glibc-common-2.17-222.el7.x86_64
glibc-2.17-222.el7.x86_64
glibc-headers-2.17-222.el7.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. Checkout & build libqb
$ git clone https://github.com/ClusterLabs/libqb.git
$ sh autogen.sh && ./configure && make && make install
2. Checkout & build kronosnet
$ git clone https://github.com/kronosnet/kronosnet.git
$ sh autogen.sh && ./configure --disable-compress-all && make && make install
3. Checkout and build corosync
$ git clone https://github.com/corosync/corosync
$ sh autogen.sh && ./configure && make && make install
Actual results:
Compilation terminates with
...
Making all in exec
make[2]: Entering directory `/home/christine/dev/corosync/exec'
CC corosync-main.o
CCLD corosync
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped
/usr/bin/ld: warning: /usr/lib64/libqb.so contains output sections; did you forget -T?
make[2]: *** [corosync] Error 1
make[2]: Leaving directory `/home/christine/dev/corosync/exec'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/christine/dev/corosync'
make: *** [all] Error 2
Expected results:
Compilation should complete successfully
Additional info:
I'm pretty certain this is down to the symbol fiddling going in in libqb, but I don't think it should segfault the linker :)
Comment 2Christine Caulfield
2018-03-16 13:44:29 UTC
I should probably point out that binutils-2.27-22.base.el7 also has the problem but binutils-2.25.1-32.base.el7_4.2.x86_64 works.
Hi Christine,
Thanks for reporting this bug.
I have uploaded a patch that fixes the problem, and an update to the
binutils.spec file so that the new patch will be included in a build.
But unfortunately the RHEL 7.5 binutils - which are the ones affected
by this bug - are now being prepared for release. So it is too late
to get this patch in. It could be released as a z-stream update once
the release is officially out, but I am not sure how critical this
problem is for you. If you are able to use the RHEL-7.4 linker to
build corosync, then is a fix for RHEL-7.5 important to you ?
Cheers
Nick
Comment 6Christine Caulfield
2018-03-19 13:09:11 UTC
Hi Nick,
Thanks for the quick response. We don't need this in RHEL7.5 fortunately because the section fiddling that's going on in libqb isn't included in that release - it does affect upstream and potentially RHEL7.6 though so a Zstream release would be very helpful.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:3032