Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-81707

libsemanage operations are 2x slower than before 3.8-1

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • libsemanage-3.8.1-1.el10_0
    • Yes
    • Critical
    • 1
    • rhel-security-selinux
    • ssg_security
    • 30
    • 2
    • QE ack
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • SELINUX 250312: 3
    • Approved Exception
    • Hide

      With the fixed version of libsemanage, the reproducer should consume about the same time as recorded with the following version: libsemanage-3.8-0.rc3.1.el10.

      Show
      With the fixed version of libsemanage, the reproducer should consume about the same time as recorded with the following version: libsemanage-3.8-0.rc3.1.el10.
    • Pass
    • Manual
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • None 

      [root@default-0 ~]# rpm -q libsemanage 
libsemanage-3.8-0.rc3.1.el10.x86_64 
[root@default-0 ~]# time semodule -B  

real    0m4.652s 
user    0m4.186s 
sys     0m0.286s 
[root@default-0 ~]# dnf update libsemanage 

Upgraded: 
 libsemanage-3.8-1.el10.x86_64  python3-libsemanage-3.8-1.el10.x86_64                                                            
Complete! 
[root@default-0 ~]# time semodule -B  

real    0m7.509s 
user    0m7.042s 
sys     0m0.424s

       

      The fix is proposed upstream

      https://lore.kernel.org/selinux/20250225075555.16136-1-lautrbach@redhat.com/

       

      And there's possibility that upstream will release 3.8.1 just with this fix

              rhn-engineering-plautrba Petr Lautrbach
              rhn-engineering-plautrba Petr Lautrbach
              Vit Mojzis Vit Mojzis
              Milos Malik Milos Malik
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: