Bug 2101151 - plymouthd was denied reading and writing to /dev/dri/card1 while booting Rawhide in a VM
Summary: plymouthd was denied reading and writing to /dev/dri/card1 while booting Rawh...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 37
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-26 03:38 UTC by Matt Fagnani
Modified: 2023-07-15 01:53 UTC (History)
8 users (show)

Fixed In Version: selinux-policy-37.22-1.fc37
Clone Of:
Environment:
Last Closed: 2023-07-15 01:53:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 1717 0 None open Allow plymouthd read/write X server miscellaneous devices 2023-05-30 09:38:29 UTC

Description Matt Fagnani 2022-06-26 03:38:45 UTC
Description of problem:

I booted Fedora-KDE-Live-x86_64-Rawhide-20220624.n.1.iso in a Gnome Boxes QEMU/KVM VM with 3 GB RAM and EFI enabled. plymouthd was denied reading and writing to /dev/dri/card1 while booting.

AVC avc: denied { read write } for pid=995 comm="plymouthd" name="card1" dev="devtmpfs" ino=469 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:xserver_misc_device_t:s0 tclass=chr_file permissive=0

ls -lZi /dev/dri/card1 showed that it had dri_device_t type in the VM, but the target context type was xserver_misc_device_t in the denial message. These denials happened both with 3D acceleration disabled using the llvmpipe mesa driver and virtio GPU and 3D acceleration enabled using the virgl mesa driver. The denials didn't appear to happen when I booted the same image on bare metal from a USB flash drive using the radeonsi mesa driver and amdgpu kernel driver with an integrated AMD Radeon R5 GPU.

Version-Release number of selected component (if applicable):
selinux-policy-37.5-1.fc37.noarch
kernel-5.19.0-0.rc3.20220623gitde5c208d533a.29.fc37.x86_64
plymouth-22.02.122-1.fc37
mesa-22.1.2-1.fc37

How reproducible:
The denials happened most of the time when booting Fedora-KDE-Live-x86_64-Rawhide-20220624.n.1.iso in a GNOME Boxes QEMU/KVM VM. I think they didn't appear if I had pressed Esc while the plymouth screen was shown during boot.

Steps to Reproduce:
1. Boot a Fedora 36 KDE Plasma installation
2. Log in to Plasma on Wayland
3. download Fedora-KDE-Live-x86_64-Rawhide-20220624.n.1.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=1993562
4. install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes
5. start GNOME Boxes 
6. boot a QEMU/KVM VM in GNOME Boxes using Fedora-KDE-Live-x86_64-Rawhide-20220624.n.1.iso with 3 GB RAM and EFI enabled

Actual results:
plymouthd was denied reading and writing to /dev/dri/card1 while booting Rawhide in a VM

Expected results:
No denials would happen.

Additional info:

Comment 1 Matt Fagnani 2022-07-26 17:47:23 UTC
Start Fedora-KDE-Live Rawhide must be selected in GRUB for this denial to appear in the journal because the plymouth screen with the spinner appears with this option as it has rhgb on the kernel command line. When Test this media & start Fedora-KDE-Live Rawhide (the default) is selected in GRUB, the plymouth screen with the spinner doesn't appear because rhgb isn't on the kernel command line, and the denial doesn't appear in the journal. This denial still happens with Fedora-KDE-Live-x86_64-Rawhide-20220725.n.1.iso.

Comment 2 Ben Cotton 2022-08-09 13:36:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 3 Fedora Update System 2023-06-29 19:59:43 UTC
FEDORA-2023-e74ea79879 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e74ea79879

Comment 4 Fedora Update System 2023-06-30 02:05:06 UTC
FEDORA-2023-e74ea79879 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e74ea79879`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e74ea79879

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-07-15 01:53:39 UTC
FEDORA-2023-e74ea79879 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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