Bug 190896
Summary: | /bin/umount changes /etc/mtab label from etc_runtime_t to etc_t | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ross Tyler <rossetyler> |
Component: | selinux-policy-targeted | Assignee: | Russell Coker <rcoker> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | dwalsh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.2.34-3.fc5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-07 10:22:49 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
Ross Tyler
2006-05-06 01:34:53 UTC
By the way, this problem is particularly bad for me as I use autofs. Per automount behavior, file systems are mounted implicitly on demand and unmounted implicitly after a period of disuse. After the first implicit umount, the /etc/mtab file is mislabeled and screws up everything afterward. The problem is really noticeable when shutting down the system and seeing all the syslog messages on the console that come when trying to umount everything. Fixed in selinux-policy-2.2.34-3.fc5 You might also want to run restorecond service restorecond start |