Bug 2350661 - enable HAVE_DEBUGINFOD_SUPPORT for perf
Summary: enable HAVE_DEBUGINFOD_SUPPORT for perf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-07 17:38 UTC by Frank Ch. Eigler
Modified: 2026-07-24 20:35 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-07-24 20:35:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2025-03-07 17:38:32 UTC
At various points in the past, the kernel rpm has been built with debuginfod client support in perf, which allows things like dwarf-based unwinding, source code fetching & annotation to work transparently.  But in recent kernels, this appears to have disappeared again.

Please consider adding a

BuildRequires: elfutils-debuginfod-client-devel

to the kernel.spec, so the perf Makefile feature auto-detection activates this functionality.

Reproducible: Always

Comment 1 Frank Ch. Eigler 2025-10-08 22:03:43 UTC
Could we please have some feedback about what is blocking adding this BuildRequires: to kernel.spec?  Over in ARK land, we did what seemed like due diligence, updating the buildroots.  What else need we do?

https://gitlab.com/cki-project/containers/-/merge_requests/630

Comment 2 Justin M. Forbes 2025-10-09 13:29:56 UTC
The current issue is that the MR was not rebased after os-build was rebased (this happens every .0 release).   But if I had to guess before that, the CKI failed because of the build root issue, and no one ever asked to have it re-run after the build root containers were changed to include it.  With a failed CKI, there was likely no one willing to take time to review it.

Comment 3 Charles Haithcock 2026-07-24 14:54:17 UTC
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. 

NOTE: This is an automated mass update.

Comment 4 Mr Beedell, Roke Julian Lockhart 2026-07-24 18:24:04 UTC
To my knowledge, this is tracked at https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3967. If someone creates an issue, at https://gitlab.com/cki-project/kernel-ark/-/work_items/new?type=Issue&initialCreationContext=list-route, and links it to that MR, then we could close this as UPSTREAM.


Note You need to log in before you can comment on or make changes to this bug.