Bug 2300320

Summary: SELinux is preventing mutter-x11-fram from read, write access on the chr_file udmabuf.
Product: [Fedora] Fedora Reporter: Zachary Moote <nuluumo>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: dwalsh, lvrabec, mmalik, nuluumo, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:561cb1e8bf37bbcabf2435237ead3562d0326d8e22f764cc498d62226b0b420f;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-29 15:35:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Zachary Moote 2024-07-29 10:08:17 UTC
Description of problem:
sudo dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/fedora39/x86_64/cuda-fedora39.repo
sudo dnf clean all
sudo dnf -y install cuda-toolkit-12-5
sudo dnf -y module install nvidia-driver:latest-dkms
SELinux is preventing mutter-x11-fram from read, write access on the chr_file udmabuf.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that mutter-x11-fram should be allowed read write access on the udmabuf chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'mutter-x11-fram' --raw | audit2allow -M my-mutterx11fram
# semodule -X 300 -i my-mutterx11fram.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:dma_device_t:s0
Target Objects                udmabuf [ chr_file ]
Source                        mutter-x11-fram
Source Path                   mutter-x11-fram
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.24-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.24-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.9.11-200.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Jul 25 18:17:34 UTC 2024
                              x86_64
Alert Count                   5
First Seen                    2024-07-28 14:58:33 EDT
Last Seen                     2024-07-29 05:46:06 EDT
Local ID                      cf7d987d-da23-4a02-881f-29fca4053230

Raw Audit Messages
type=AVC msg=audit(1722246366.426:183): avc:  denied  { read write } for  pid=2223 comm="mutter-x11-fram" name="udmabuf" dev="devtmpfs" ino=188 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dma_device_t:s0 tclass=chr_file permissive=0


Hash: mutter-x11-fram,xdm_t,dma_device_t,chr_file,read,write

Version-Release number of selected component:
selinux-policy-targeted-40.24-1.fc40.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing mutter-x11-fram from read, write access on the chr_file udmabuf.
package:        selinux-policy-targeted-40.24-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.9.11-200.fc40.x86_64
event_log:      2024-07-29-06:06:05> Looking for similar problems in bugzilla
component:      selinux-policy

Comment 1 Zachary Moote 2024-07-29 10:08:19 UTC
Created attachment 2040672 [details]
File: description

Comment 2 Zachary Moote 2024-07-29 10:08:21 UTC
Created attachment 2040673 [details]
File: os_info

Comment 3 Zdenek Pytela 2024-07-29 15:35:21 UTC

*** This bug has been marked as a duplicate of bug 2300176 ***