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.
DescriptionEdjunior Barbosa Machado
2022-01-24 17:06:53 UTC
Created attachment 1853117[details]
annocheck output
Description of problem:
Latest go-rpm-macros-3.0.9-9.el9 build fails on annocheck test, part of rhel-9.0 rpminspect static analysis, with the following:
(...)
annocheck: Version 10.44.
Hardened: /usr/libexec/go-rpm-macros/golist: PASS: pie test
Hardened: /usr/libexec/go-rpm-macros/golist: PASS: writable-got test
Hardened: /usr/libexec/go-rpm-macros/golist: PASS: dynamic-segment test
Hardened: /usr/libexec/go-rpm-macros/golist: FAIL: bind-now test because not linked with -Wl,-z,now
Hardened: /usr/libexec/go-rpm-macros/golist: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-bind-now.html
(...)
The test fails only on aarch64 and x86_64 - it passes on s390x and ppc64le.
Version-Release number of selected component (if applicable):
go-rpm-macros-3.0.9-9.el9
This is very strange. Annocheck does appear to be correct in its issuing
of a FAIL result. For example looking at the dynamic information for the
ppc64le version of golist shows:
% readelf -d usr.ppc64le/libexec.ro-rpm-macros/golist
File: usr.ppc64le/libexec/go-rpm-macros/golist
Dynamic section at offset 0x3cfb78 contains 29 entries:
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
[...]
0x0000000000000018 (BIND_NOW)
0x000000006ffffffb (FLAGS_1) Flags: NOW PIE
[...]
Whereas the x86_64 version of the same binary shows:
% readelf -d usr.x86_64/libexec/go-rpm-macros/golist
File: usr.x86_64/libexec/go-rpm-macros/golist
Dynamic section at offset 0x3b5040 contains 12 entries:
Tag Type Name/Value
0x0000000000000004 (HASH) 0x677de0
[...]
0x000000006ffffffb (FLAGS_1) Flags: PIE
[...]
So no NOW bit in the FLAGS_1 field and no BIND_NOW field.
However the final link command lines in the build logs appear to be the same:
From the ppc64le build.log:
go build -buildmode pie -compiler gc '-tags=rpm_crashtraceback ' -ldflags ' -B 0xbac2d7e5f21245b5f6ce832dacf49a6d1c2d7c32 -extldflags '\''-Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\''' -a -v -o /builddir/build/BUILD/golist-0.10.1/_build/bin/golist pagure.io/golist/cmd/golist
From the x86_64 build log:
go build -buildmode pie -compiler gc '-tags=rpm_crashtraceback ' -ldflags ' -B 0xf87b852735fda3e6ef437632790c629bf7cf94dd -extldflags '\''-Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\''' -a -v -o /builddir/build/BUILD/golist-0.10.1/_build/bin/golist pagure.io/golist/cmd/golist
I can only theorize that the x86_64 GO compiler is doing something different
when constructing the actual command line that is passed to the linker. Is
there a way to ask GO to explicitly display the linker command line ?
Comment 8RHEL Program Management
2023-07-24 07:28:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 10RHEL Program Management
2023-09-22 16:31:34 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 11RHEL Program Management
2023-09-22 16:31:54 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.