Description of problem: SELinux is preventing mdadm from 'getattr' accesses on the directory /dev/binderfs. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mdadm should be allowed getattr access on the binderfs directory 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 '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:binderfs_t:s0 Target Objects /dev/binderfs [ dir ] Source mdadm Source Path mdadm Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-42.16-1.fc43.noarch Local Policy RPM selinux-policy-targeted-42.16-1.fc43.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.17.8-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 14 01:47:12 UTC 2025 x86_64 Alert Count 1149 First Seen 2025-11-21 19:56:36 EST Last Seen 2025-11-26 00:00:09 EST Local ID 6d46e2da-a568-4372-a92e-4ca614990a13 Raw Audit Messages type=AVC msg=audit(1764133209.590:19111): avc: denied { getattr } for pid=1898232 comm="mdadm" path="/dev/binderfs" dev="binder" ino=1 scontext=system_u:system_r:mdadm_t:s0 tcontext=system_u:object_r:binderfs_t:s0 tclass=dir permissive=0 Hash: mdadm,mdadm_t,binderfs_t,dir,getattr Version-Release number of selected component: selinux-policy-targeted-42.16-1.fc43.noarch Additional info: reporter: libreport-2.17.15 hashmarkername: setroubleshoot kernel: 6.17.8-300.fc43.x86_64 reason: SELinux is preventing mdadm from 'getattr' accesses on the directory /dev/binderfs. component: selinux-policy type: libreport package: selinux-policy-targeted-42.16-1.fc43.noarch component: selinux-policy
Created attachment 2116250 [details] File: os_info
Created attachment 2116251 [details] File: description
*** This bug has been marked as a duplicate of bug 2417293 ***