This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2150032 - abidiff is taking a very long time on /usr/bin/ld.gold and /usr/bin/dwp
Summary: abidiff is taking a very long time on /usr/bin/ld.gold and /usr/bin/dwp
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libabigail
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dodji Seketeli
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On: 2152553
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-01 16:52 UTC by David Cantrell
Modified: 2023-09-22 15:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 15:58:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7323 0 None Migrated None 2023-09-22 15:58:17 UTC
Red Hat Issue Tracker RHELPLAN-141065 0 None None None 2022-12-01 16:59:16 UTC

Description David Cantrell 2022-12-01 16:52:27 UTC 
When running rpminspect to compare binutils-2.35.2-24.el9 to binutils-2.35.2-26.el9, the abidiff inspection gets hung up on /usr/bin/ld.gold and /usr/bin/dwp and has taken up to 8 hours before ever completing.

Configuring rpminspect to exclude these two files from the abidiff run causes rpminspect to complete as expected.

More information is here:
https://issues.redhat.com/browse/OSCI-4219
Comment 1 William Cohen 2022-12-01 19:21:07 UTC 
On Fedora 36 machine with following rpms see libagigail getting stuck on ld.gold:

rpminspect-1.11-0.1.202211231559git683d045.fc36.x86_64
libabigail-2.1-1.fc36.x86_64

With the following:

rpminspect -v -T abidiff -a x86_64 -w $(pwd)/tmp binutils-2.35.2-24.el9  binutils-2.35.2-26.el9 -c /usr/share/rpminspect/redhat.yaml


After 9 minutes of runtime I killed the abidiff that was running for ld.gold.  It continue on to processing dwp, but libabigail completed processing dwp.

One question that crossed my mind was whether the fixes for rhbz2134960 in libabigail-2.2 to speed up processing of firefox libraries address this problem?
I installed a locally built version of libabigail-2.2-1.el9.src.rpm and reran.  The rpminspect command completed in a reasonable amount of time on a F36 machine.
Comment 5 Dodji Seketeli 2022-12-02 21:59:39 UTC 
OK, t(In reply to William Cohen from comment #1)
> On Fedora 36 machine with following rpms see libagigail getting stuck on
> ld.gold:
> 
> rpminspect-1.11-0.1.202211231559git683d045.fc36.x86_64
> libabigail-2.1-1.fc36.x86_64
> 
> With the following:
> 
> rpminspect -v -T abidiff -a x86_64 -w $(pwd)/tmp binutils-2.35.2-24.el9 
> binutils-2.35.2-26.el9 -c /usr/share/rpminspect/redhat.yaml
> 
> 
> After 9 minutes of runtime I killed the abidiff that was running for
> ld.gold.  It continue on to processing dwp, but libabigail completed
> processing dwp.
> 
> One question that crossed my mind was whether the fixes for rhbz2134960 in
> libabigail-2.2 to speed up processing of firefox libraries address this
> problem?
> I installed a locally built version of libabigail-2.2-1.el9.src.rpm and
> reran.  The rpminspect command completed in a reasonable amount of time on a
> F36 machine.


Thank you Will!

I have made an upstream 2.2 release containing all the latest fixes including the ones for rhbz2134960.  The release notes are available at https://inbox.sourceware.org/libabigail/87o7slsd5o.fsf@redhat.com.

In case someone is interested, here is a centos 9 scratch-build for that release: https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=1648613.

At this point, I think we can tout the idea of an EL 9.2 rebase to libabigail 2.2, if that scratch-build improves things.
Comment 6 RHEL Program Management 2023-09-22 15:55:36 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 7 RHEL Program Management 2023-09-22 15:58:24 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.
Note You need to log in before you can comment on or make changes to this bug.