Bug 2224058 - librsvg2: does not properly support CET
Summary: librsvg2: does not properly support CET
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: librsvg2
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-19 17:03 UTC by Siddhesh Poyarekar
Modified: 2025-05-16 07:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-16 07:42:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Siddhesh Poyarekar 2023-07-19 17:03:17 UTC
Since rust does not have stable support for CET yet, librsvg2 is not built with shadow stack support and hence lacks the SHSTK markup in the library.

Without this, when Fedora is booted with a shadow stack enabled kernel (patches are currently in review upstream[1]), a number of php and python packages fail to build.

[1] https://lore.kernel.org/lkml/20230613001108.3040476-1-rick.p.edgecombe@intel.com/

Reproducible: Always

Comment 1 Fedora Release Engineering 2023-08-16 07:19:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Juro Bystricky 2023-10-19 23:47:56 UTC
Also in CentOS Stream 9 we get:
Failed to load shared library 'libtimezonemap.so.1' referenced by the typelib: /lib64/librsvg-2.so.2: rebuild shared object with SHSTK support enabled

Comment 3 Siddhesh Poyarekar 2023-10-20 12:20:20 UTC
@Juro, that shouldn't happen, what glibc are you running?  We don't have userspace runtime SHSTK support in glibc yet, not even upstream.

Comment 4 Juro Bystricky 2023-10-20 13:43:20 UTC
(In reply to Siddhesh Poyarekar from comment #3)
> @Juro, that shouldn't happen, what glibc are you running?  We don't have
> userspace runtime SHSTK support in glibc yet, not even upstream.

Sorry, I forgot to mention we use a patched glibc with user mode shadow stack (SHSTK) support.(glibc is based on Fedora).
As a part of our internal testing we try to preemptively detect any SHSTK issues.

Comment 5 Siddhesh Poyarekar 2023-10-20 15:02:03 UTC
Thanks for confirmng, so that's unrelated. This bug specifically tracks this issue for Fedora.

Comment 6 Aoife Moloney 2024-02-15 22:56:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 7 Aoife Moloney 2025-04-25 10:06:10 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Aoife Moloney 2025-05-16 07:42:26 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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