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.

Bug 2224410

Summary: /usr/lib64/ceph/libceph-common.so.2: rebuild shared object with SHSTK support enabled
Product: Red Hat Enterprise Linux 9 Reporter: Juro Bystricky <juro.bystricky>
Component: cephAssignee: Boris Ranto <branto>
Status: CLOSED MIGRATED QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-05 17:33:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Juro Bystricky 2023-07-20 17:24:05 UTC
Description of problem:
We anticipate CET support being merged into upstream Linux kernel in the near future:
https://www.phoronix.com/news/Linux-6.4-Shadow-Stack-Coming

While testing CentOS Stream 9 with custom kernel and glibc, both with shadow stack enabled, we were not able to start libvirtd service.


Version-Release number of selected component (if applicable):
The library that needs to be rebuilt with shadow stack enabled is provided by the package librados2:

$ dnf provides /usr/lib64/ceph/libceph-common.so.2
librados2-2:16.2.4-5.el9.x86_64 : RADOS distributed object store client library
Repo        : @System
Matched from:
Filename    : /usr/lib64/ceph/libceph-common.so.2


How reproducible:
100%

Steps to Reproduce:
1. Boot CS9 with Linux kernel + glibc with CET enabled
2. $ sudo systemctl start libvirtd
3. $ sudo systemctl status libvirtd
3. $ sudo journalctl -ef

libvirtd[42601]: internal error: Failed to load module '/usr/lib64/libvirt/storage-backend/libvirt_storage_backend_rbd.so': /usr/lib64/ceph/libceph-common.so.2: rebuild shared object with SHSTK support enabled
Jul 20 12:30:14 gnr-bkc systemd[1]: libvirtd.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED


Actual results:
libvirtd fails to run

Expected results:
libvirtd running

Comment 1 RHEL Program Management 2023-09-05 17:32:59 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 2 RHEL Program Management 2023-09-05 17:33:26 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.