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.
Description of problem:
The latest run of upstream test suite reports following failed ld test cases:
FAIL: Build plt-main
FAIL: Build plt-main with PIE
FAIL: Build plt-main with PIE and -z bndplt
FAIL: Build plt-main with -z bndplt
FAIL: ld-x86-64/pltgot-1
FAIL: ld-x86-64/pltgot-2
I saved the whole buildroot (test suite was started after `rpmbuild -bb` in rpmbuild's BUILD) if it's of any help. If not, please let me know what'd help and I try to update my test suite wrapper to include such info.
Version-Release number of selected component (if applicable):
binutils-2.27-40.base.el7
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Hi Miloš,
> FAIL: Build plt-main> I saved the whole buildroot (test suite was started after `rpmbuild -bb` in
> rpmbuild's BUILD) if it's of any help.
Yes - are you able to upload the ld.log file from the failing linker tests ?
In particular I want to find out why the build of plt-main failed, as this
is probably the cause of all of the following failures as well.
Cheers
Nick
(In reply to Nick Clifton from comment #2)
> Hi Miloš,
>
> > FAIL: Build plt-main
>
>
> > I saved the whole buildroot (test suite was started after `rpmbuild -bb` in
> > rpmbuild's BUILD) if it's of any help.
>
> Yes - are you able to upload the ld.log file from the failing linker tests ?
> In particular I want to find out why the build of plt-main failed, as this
> is probably the cause of all of the following failures as well.
>
> Cheers
> Nick
Oh, I forgot to link the saved buildroot in the report :(
https://beaker.engineering.redhat.com/recipes/6729575/tasks/91015902/logs/buildroot.tgz
And extracted ld.log is here: http://nest.test.redhat.com/mnt/qa/scratch/mprchlik/bz1699745-ld.log
Hi Milos,
OK, I have managed to reproduce the problem and determine the cause.
Fortunately the issue is a mistake in the linker testsuite. Or more
precisely it is a mistake in the patch that disables the generation
of the R_X86_64_GOTPCRELX relocs. This patch changes the relocations
that are generated by the linker, but it failed to update the testsuite
to take this into account. (Actually the patch does update the
testsuite, but it missed these checks).
I will create a patch to fix the tests and check it in once it is ready.
Cheers
Nick
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-2019:2075