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.
DescriptionJerry Snitselaar
2021-10-21 14:54:46 UTC
Description of problem:
I'm seeing this in osci:
Hardened: /usr/lib64/libaccel-config.so.1.0.0: gap: (0x4a90..0xafb8
probable component: do_log) in annobin notes.
Hardened: /usr/lib64/libaccel-config.so.1.0.0: FAIL: notes test because
gaps were detected in the annobin coverage
Looking at the build it looks like the annobin spec file is being
referenced in the compiler and linker commands, so I'm not sure what
is causing this complaint.
https://kojihub.stream.rdu2.redhat.com/kojifiles/work/tasks/1439/731439/build.log
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
libaccel-config.so.1.0.0 was the only reproducer I was aware of
so I tried to examine it on all the architectures even though
we build and ship it on x86_64 only. I don't mind limiting this
ticket to x86_64 if you decide that the problem on the other
architectures is purely theoretical and doesn't matter in
practice.
Regarding the building issue I'm afraid I can't help with that.
However I built it on two different machines, no problem
whatsoever. I can share my today's machine, just ping me on IRC.
I'll attach both the SO file and a RPM list.
Doh - I totally forgot that I had run into a problem with this fix that was specific to the PPC64LE. So there is code in annobin plugin that disables the fix just for that target.
Fortunately there is a workaround. Testing it now....
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 (new packages: annobin), 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/RHEA-2022:2342