Hide Forgot
Description of problem: SELinux popped up a block message saying that smartd had violated the rules. I suspect that smartd is behaving properly and that SELinux is at fault, but I haven't the slightest bit of proof. Version-Release number of selected component (if applicable): How reproducible: Don't know; I have had the system running for fifteen or twenty minutes and it just popped up. However, it didn't happen previously when I had the system running far longer. Steps to Reproduce: 1. Probably crucial, run 'hdparm -S 6 /dev/sdb'; this causes the drive motor to spin down after 30 seconds of inactivity. I did _not_ do that previously but _did_ do that today, and got the error shortly after that. 2. run 'hdparm -C /dev/sdb' to confirm that it has spun down 3. Some minutes later the error message popped up. Actual results: See attached SELinux report. Expected results: Additional info: This is with the April beta; I will try to reproduce it with this month's Preview release.
Created attachment 304823 [details] SELinux error report
You can allow this for now. # audit2allow -M mypol -l -i /var/log/audit/audit.log # semodule -i mypol.pp Fixed in selinux-policy-3.3.1-48.fc9.noarch