Bug 1285916

Summary: SELinux should allow BTRFS_IOC_SNAP_DESTROY ioctl on tmpfiles
Product: [Fedora] Fedora Reporter: dylanxmackenzie
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 23CC: dominick.grift, dwalsh, dylanxmackenzie, lvrabec, mgrepl, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 16:20:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dylanxmackenzie 2015-11-27 00:30:14 UTC
Description of problem:
On a fresh installation of fedora 23 on btrfs with SELinux enabled, a systemd-tmpfiles-setup was failing after a call to ioctl returned EPERM. I filed an issue on the systemd github (link in additional info), and the problem was determined to be that selinux doesn't allow the BTRFS_IOC_SNAP_DESTROY ioctl on objects of type user_tmp_t.

Version-Release number of selected component (if applicable):
selinux-policy 3.13.1-154.fc23

How reproducible:
Very

Steps to Reproduce:
1. Install fedora 23 on a btrfs filesystem.
2. Run any dnf command as a non-root user (i.e. `dnf list installed`).
3. Attempt to do `systemd-tmpfiles --remove dnf.conf`

Actual results:
Fails with Operation Not Permitted

Expected results:
Should remove directory in /var/tmp/dnf-`whoami`-xxxxxxxx/locks

Additional info:
https://github.com/systemd/systemd/issues/2025

Comment 1 dylanxmackenzie 2015-11-27 00:34:43 UTC
Sorry, I meant 'systemd-tmpfiles-setup.service was failing' instead of 'a systemd-tmpfiles-setup was failing'

Comment 2 Daniel Walsh 2015-12-01 20:37:35 UTC
What avc are you seeing? 

ausearch -m avc -ts recent

Comment 3 Fedora Admin XMLRPC Client 2016-09-27 14:57:23 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2016-11-24 13:46:21 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2016-12-20 16:20:11 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Red Hat Bugzilla 2023-09-14 03:13:55 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days