Bug 928582
Summary: | SELinux is preventing /usr/bin/touch from 'write' accesses on the directory lock. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | sangu <sangu.fedora> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | awilliam, decathorpe, dominick.grift, dwalsh, dzrudy, ed.greshko, kkshethin, mail, me, mgrepl, PTrenholme, stefw, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:f3552813e0d1d4547f5f5ef3a739abbe0efa86c9d8105361b84a76f30d378b5c | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-19 05:54:20 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: |
Description
sangu
2013-03-28 01:45:02 UTC
Looks like /run/lock is mislabled. restorecon -R -v /run/lock Description of problem: Not sure, But, in any case, shouldn't any application be able to set and release locks? Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport (In reply to comment #1) > Looks like /run/lock is mislabled. > > restorecon -R -v /run/lock Yesterday # ls -Z /run/lock drwxrwxr-x. root lock system_u:object_r:var_run_t:s0 lockdev drwx------. root root system_u:object_r:var_run_t:s0 lvm drwxr-xr-x. root root system_u:object_r:pppd_lock_t:s0 ppp drwxr-xr-x. root root system_u:object_r:var_run_t:s0 subsys # ls -Zd /run/lock drwxr-xr-x. root root system_u:object_r:var_run_t:s0 /run/lock # restorecon -R -v /run/lock/ restorecon reset /run/lock/ppp context system_u:object_r:pppd_lock_t:s0->system_u:object_r:var_run_t:s0 # ls -Zd /run/lock drwxr-xr-x. root root system_u:object_r:var_run_t:s0 /run/lock # ls -Z /run/lock drwxrwxr-x. root lock system_u:object_r:var_run_t:s0 lockdev drwx------. root root system_u:object_r:var_run_t:s0 lvm drwxr-xr-x. root root system_u:object_r:var_run_t:s0 ppp drwxr-xr-x. root root system_u:object_r:var_run_t:s0 subsys Today, this issue still happens. 3월 30 11:38:02 None anacron[4147]: Job `cron.daily' started 3월 30 11:38:02 None run-parts(/etc/cron.daily)[5817]: starting logrotate 3월 30 11:38:02 None run-parts(/etc/cron.daily)[5822]: finished logrotate 3월 30 11:38:02 None run-parts(/etc/cron.daily)[5824]: starting man-db.cron 3월 30 11:38:02 None setroubleshoot[791]: dbus avc(node=None type=AVC msg=audit(1364611082.323:449): avc: denied { write } for pid=5829 comm="touch" name="lock" dev="tmpfs" ino=6744 scontext=system_u:system_ 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.feed() got node=None type=AVC msg=audit(1364611082.323:449): avc: denied { write } for pid=5829 comm="touch" name="lock" dev="tmpfs" ino=6744 sco 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.add_record_to_cache(): node=None type=AVC msg=audit(1364611082.323:449): avc: denied { write } for pid=5829 comm="touch" name="lock" dev="tmpfs" 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.feed() got node=None type=SYSCALL msg=audit(1364611082.323:449): arch=c000003e syscall=2 success=no exit=-13 a0=7fff5fbfef39 a1=941 a2=1b6 a3=7fff5f 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.add_record_to_cache(): node=None type=SYSCALL msg=audit(1364611082.323:449): arch=c000003e syscall=2 success=no exit=-13 a0=7fff5fbfef39 a1=941 a2=1 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.feed() got node=None type=EOE msg=audit(1364611082.323:449): 3월 30 11:38:02 None setroubleshoot[791]: AuditRecordReceiver.add_record_to_cache(): node=None type=EOE msg=audit(1364611082.323:449): 3월 30 11:38:02 None setroubleshoot[791]: analyze_avc() avc=scontext=system_u:system_r:mandb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 access=['write'] tclass=dir tpath=lock 3월 30 11:38:02 None setroubleshoot[791]: lookup_signature: found 1 matches with scores 1.00 3월 30 11:38:02 None setroubleshoot[791]: signature found in database 3월 30 11:38:02 None setroubleshoot[791]: sending alert to all clients 3월 30 11:38:02 None setroubleshoot[791]: SELinux is preventing /usr/bin/touch from write access on the directory lock. For complete SELinux messages. run sealert -l a33e6d2e-4466-4652-8c0f-d32f9c705a6b Fixed in selinux-policy-3.12.1-25.fc19.noarch Description of problem: Pressed reload firewalld button in the Firewall configuration utility. Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport Description of problem: Happened when man-db.cron ran. Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport Description of problem: Happens on install and reboot of F19 Alpha TC5 KDE desktop live. No user interaction needed. Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport Description of problem: Error occured while system idle in KDE Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport Fixed in selinux-policy-3.12.1-27.fc19 selinux-policy-3.12.1-28.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2013-5045/selinux-policy-3.12.1-28.fc19 Package selinux-policy-3.12.1-28.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-28.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5045/selinux-policy-3.12.1-28.fc19 then log in and leave karma (feedback). selinux-policy-3.12.1-28.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |