Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: F33 update pulled selinux-policy-3.14.6-38.fc33.noarch (from selinux-policy-3.14.6-37.fc33.noarch) After a reboot, two alerts came up for mdadm accessing (search, read) a "directory" of "dma_heap". SELinux is preventing mdadm from 'search' accesses on the katalog dma_heap. ***** Plugin catchall (100. confidence) suggests ************************** Aby mdadm powinno mieć domyślnie search dostęp do dma_heap directory. Then proszę to zgłosić jako błąd. Można utworzyć lokalny moduł polityki, aby umożliwić ten dostęp. Do można tymczasowo zezwolić na ten dostęp wykonując polecenia: # ausearch -c 'mdadm' --raw | audit2allow -M my-mdadm # semodule -X 300 -i my-mdadm.pp Additional Information: Source Context system_u:system_r:mdadm_t:s0 Target Context system_u:object_r:dma_device_t:s0 Target Objects dma_heap [ dir ] Source mdadm Source Path mdadm Port <Nieznane> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM <Nieznane> Local Policy RPM selinux-policy-targeted-3.14.6-38.fc33.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.12.11-200.fc33.x86_64 #1 SMP Wed Jun 16 16:10:53 UTC 2021 x86_64 x86_64 Alert Count 3 First Seen 2021-06-17 17:19:33 CEST Last Seen 2021-06-17 20:25:52 CEST Local ID 093ce7ce-c170-4331-bea0-d9651fc20694 Raw Audit Messages type=AVC msg=audit(1623954352.156:155): avc: denied { search } for pid=1009 comm="mdadm" name="dma_heap" dev="devtmpfs" ino=148 scontext=system_u:system_r:mdadm_t:s0 tcontext=system_u:object_r:dma_device_t:s0 tclass=dir permissive=0 Hash: mdadm,mdadm_t,dma_device_t,dir,search Additional info: component: selinux-policy reporter: libreport-2.14.0 hashmarkername: setroubleshoot kernel: 5.12.11-200.fc33.x86_64 type: libreport
Guessing duplicates: https://bugzilla.redhat.com/show_bug.cgi?id=1970744 https://bugzilla.redhat.com/show_bug.cgi?id=1971517 https://bugzilla.redhat.com/show_bug.cgi?id=1973324
*** This bug has been marked as a duplicate of bug 1965743 ***