Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515178 - SELinux is preventing node from using the 'execmem' accesses on a process.
Summary: SELinux is preventing node from using the 'execmem' accesses on a process.
Alias: None
Product: Fedora
Classification: Fedora
Component: smartmontools
Version: 27
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:266ace3860588b217900d3ef2d5...
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-20 10:37 UTC by Konrad Paumann
Modified: 2018-11-30 22:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 22:38:54 UTC

Attachments (Terms of Use)

Description Konrad Paumann 2017-11-20 10:37:23 UTC
Description of problem:
it happened while restarting gnome shell (ALT F2 -> 'r')
SELinux is preventing node from using the 'execmem' accesses on a process.

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

If you believe that node should be allowed execmem access on processes labeled fsdaemon_t by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# ausearch -c 'node' --raw | audit2allow -M my-node
# semodule -X 300 -i my-node.pp

Additional Information:
Source Context                system_u:system_r:fsdaemon_t:s0
Target Context                system_u:system_r:fsdaemon_t:s0
Target Objects                Unknown [ process ]
Source                        node
Source Path                   node
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-260.13.fc26.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.13.11-200.fc26.x86_64 #1 SMP Thu
                              Nov 2 18:28:35 UTC 2017 x86_64 x86_64
Alert Count                   8
First Seen                    2017-11-06 13:10:00 CET
Last Seen                     2017-11-15 21:21:28 CET
Local ID                      e4473949-a86b-4265-b88f-3c28aaa75c11

Raw Audit Messages
type=AVC msg=audit(1510777288.703:646): avc:  denied  { execmem } for  pid=8864 comm="node" scontext=system_u:system_r:fsdaemon_t:s0 tcontext=system_u:system_r:fsdaemon_t:s0 tclass=process permissive=0

Hash: node,fsdaemon_t,fsdaemon_t,process,execmem

Version-Release number of selected component:

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.13.13-300.fc27.x86_64
type:           libreport

Comment 1 Lukas Vrabec 2017-11-20 10:53:20 UTC

Is there any reason why fsdaemon needs execmem? This SELinux says that fsdaemon is trying to make executable an anonymous mapping or private file mapping that is

Comment 2 Ben Cotton 2018-11-27 14:33:56 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 3 Ben Cotton 2018-11-30 22:38:54 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.