Bug 1555142

Summary: SELinux is preventing (coredump) from 'remount' accesses on the filesystem .
Product: [Fedora] Fedora Reporter: Parag Nemade <pnemade>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: dwalsh, jonha87, jsmith.fedora, lvrabec, mgrepl, plautrba, pmoore, sjoerd
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d71b641915fd5c7ba3d4a37651334da545244573efd45916b287a7ffed007bd;VARIANT_ID=workstation;
Fixed In Version: selinux-policy-3.14.1-18.fc28 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-26 22:31:51 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 Parag Nemade 2018-03-14 03:13:41 UTC
Description of problem:
I did execute the " restorecon -Rv /" to fix lables on my system but still this issue is ocurring
SELinux is preventing (coredump) from 'remount' accesses on the filesystem .

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

If you believe that (coredump) should be allowed remount access on the  filesystem by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c '(coredump)' --raw | audit2allow -M my-coredump
# semodule -X 300 -i my-coredump.pp

Additional Information:
Source Context                system_u:system_r:init_t:s0
Target Context                system_u:object_r:unlabeled_t:s0
Target Objects                 [ filesystem ]
Source                        (coredump)
Source Path                   (coredump)
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.14.1-13.fc28.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.16.0-0.rc5.git0.1.fc28.x86_64 #1
                              SMP Mon Mar 12 20:10:40 UTC 2018 x86_64 x86_64
Alert Count                   122
First Seen                    2018-03-08 09:19:57 IST
Last Seen                     2018-03-14 08:38:55 IST
Local ID                      a2c963ae-809b-4190-a8bd-2b28d2c32e09

Raw Audit Messages
type=AVC msg=audit(1520996935.724:308): avc:  denied  { remount } for  pid=3509 comm="(-localed)" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=0


Hash: (coredump),init_t,unlabeled_t,filesystem,remount

Version-Release number of selected component:
selinux-policy-3.14.1-13.fc28.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.16.0-0.rc5.git0.1.fc28.x86_64
type:           libreport

Potential duplicate: bug 1554000

Comment 1 Parag Nemade 2018-03-14 03:16:38 UTC
Is there any way to self-access and find that I need to run "restorecon -Rv /"?
Is it not possible to create any legitimate policy for such coredump issues?

Comment 2 Parag Nemade 2018-03-14 04:59:17 UTC
This is just not stopping, I have executed this exact command
sudo restorecon -Rv /

still getting notifications.

Comment 3 Sjoerd Mullender 2018-03-14 09:28:06 UTC
Description of problem:
When a program (any program) crashes and dumps core, this alert pops up.
Easy way to reproduce:
sleep 10
hit control-backslash to send a SIGQUIT to the sleep.

Version-Release number of selected component:
selinux-policy-3.14.1-11.fc28.noarch

Additional info:
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.16.0-0.rc4.git0.1.fc28.x86_64
type:           libreport

Comment 4 Lukas Vrabec 2018-03-14 09:44:33 UTC
*** Bug 1554462 has been marked as a duplicate of this bug. ***

Comment 5 Jonathan Haas 2018-03-16 11:15:28 UTC
Description of problem:
Popped up after launching gnome-boxes

Version-Release number of selected component:
selinux-policy-3.14.1-13.fc28.noarch

Additional info:
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.16.0-0.rc5.git0.1.fc28.x86_64
type:           libreport

Comment 6 Jonathan Haas 2018-03-16 13:13:11 UTC
Description of problem:
Doing nothing (was away from pc)

Version-Release number of selected component:
selinux-policy-3.14.1-13.fc28.noarch

Additional info:
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.16.0-0.rc5.git0.1.fc28.x86_64
type:           libreport

Comment 7 Fedora Update System 2018-03-25 13:11:53 UTC
selinux-policy-3.14.1-17.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b8cb71b345

Comment 8 Fedora Update System 2018-03-25 20:32:45 UTC
selinux-policy-3.14.1-17.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b8cb71b345

Comment 9 Fedora Update System 2018-03-26 21:51:29 UTC
selinux-policy-3.14.1-18.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7821b2e7c4

Comment 10 Fedora Update System 2018-03-26 22:31:51 UTC
selinux-policy-3.14.1-18.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.