Red Hat Bugzilla – Bug 842195
yum snapshots security context problem in btrfs /home
Last modified: 2013-08-01 12:25:56 EDT
Description of problem:
After uninstalling yum snapshots in encrypted btrfs /home,
the directories in /home are not removable by superuser or user.
chown has no effect due to context: system_u:object_r: s0
Version-Release number of selected component (if applicable):
0 selinux enforcing
1. install F17 with encrypted btrfs /home with 10 GB data (say)
2. keep on updating over a few days.
3. Many snapshots occupying considerable space would result.
4. The contents may be deletable by superuser, but not the directories
5. Uninstall the yum snapshot plugin
6. system_u:object_r: s0
Steps to Reproduce:
Have you tried to run restorecon -R -v /home? Can you try in permissive mode if this does not work. This looks like you have somehow gotten a bad label into brtfs, this could be a bug in btrfs also.
Yes, that does not change the context and even if I do it from outside (Scientific Linux-6.2).
drwxr-xr-x. <username> 1000 system_u:object_r:home_root_t:s0 /media/abc/yum_20120630071356
I have no idea how those labels got onto the file system. Very strange.
just checking: you've tried deleting using
btrfs su del /media/abc/yum_20120630071356
Yes, I tried btrfs subvolume delete.
Btw, this partition was from F16 and was created much earlier. So the bug should be duplicated first.
Seems like a kernel issue to me.
is this still a problem in current release ?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.