Bug 1650632 - SELinux is preventing mount from 'read' accesses on the blk_file loop0.
Summary: SELinux is preventing mount from 'read' accesses on the blk_file loop0.
Alias: None
Product: Fedora
Classification: Fedora
Component: snapd
Version: 29
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Zygmunt Krynicki
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2b4d1729e8f7469d59dfa27fce7...
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-16 16:53 UTC by Lucas M. Rodrigues
Modified: 2019-11-27 22:15 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 22:15:06 UTC
Type: ---

Attachments (Terms of Use)

Description Lucas M. Rodrigues 2018-11-16 16:53:45 UTC
Description of problem:
SELinux is preventing mount from 'read' accesses on the blk_file loop0.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that mount should be allowed read access on the loop0 blk_file by default.
Then você deve informar que este é um erro.
Você pode gerar um módulo de política local para permitir este acesso.
allow this access for now by executing:
# ausearch -c 'mount' --raw | audit2allow -M my-mount
# semodule -X 300 -i my-mount.pp

Additional Information:
Source Context                system_u:system_r:snappy_t:s0
Target Context                system_u:object_r:fixed_disk_device_t:s0
Target Objects                loop0 [ blk_file ]
Source                        mount
Source Path                   mount
Port                          <Desconhecido>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.14.2-42.fc29.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.18.16-300.fc29.x86_64 #1 SMP Sat
                              Oct 20 23:24:08 UTC 2018 x86_64 x86_64
Alert Count                   1
First Seen                    2018-11-16 14:01:41 -02
Last Seen                     2018-11-16 14:01:41 -02
Local ID                      cc31b51b-685f-400e-9049-2ce3a3fbeaed

Raw Audit Messages
type=AVC msg=audit(1542384101.348:534): avc:  denied  { read } for  pid=27777 comm="mount" name="loop0" dev="devtmpfs" ino=128391 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:fixed_disk_device_t:s0 tclass=blk_file permissive=1

Hash: mount,snappy_t,fixed_disk_device_t,blk_file,read

Version-Release number of selected component:

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.6
hashmarkername: setroubleshoot
kernel:         4.18.16-300.fc29.x86_64
type:           libreport

Potential duplicate: bug 1626150

Comment 1 Ben Cotton 2019-10-31 19:30:22 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 2 Ben Cotton 2019-11-27 22:15:06 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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

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

Note You need to log in before you can comment on or make changes to this bug.