Bug 1315105

Created attachment 1133547 [details]
File: backtrace

Created attachment 1133548 [details]
File: cgroup

Created attachment 1133549 [details]
File: core_backtrace

Created attachment 1133550 [details]
File: dso_list

Created attachment 1133551 [details]
File: environ

Created attachment 1133552 [details]
File: exploitable

Created attachment 1133553 [details]
File: limits

Created attachment 1133554 [details]
File: maps

Created attachment 1133555 [details]
File: mountinfo

Created attachment 1133556 [details]
File: namespaces

Created attachment 1133557 [details]
File: open_fds

Created attachment 1133558 [details]
File: proc_pid_status

Created attachment 1133559 [details]
File: var_log_messages

SELinux is preventing systemd-logind from getattr access on the file /dev/shm/lldpad.state.

*****  Plugin restorecon (99.5 confidence) suggests   ************************

If you want to fix the label. 
/dev/shm/lldpad.state default label should be lldpad_tmpfs_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /dev/shm/lldpad.state

*****  Plugin catchall (1.49 confidence) suggests   **************************

If you believe that systemd-logind should be allowed getattr access on the lldpad.state file 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:
# grep systemd-logind /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:systemd_logind_t:s0
Target Context                system_u:object_r:tmpfs_t:s0
Target Objects                /dev/shm/lldpad.state [ file ]
Source                        systemd-logind
Source Path                   systemd-logind
Port                          <Unknown>
Host                          hgst500.touro
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-158.7.fc23.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     hgst500.touro
Platform                      Linux hgst500.touro 4.4.2-301.fc23.x86_64 #1 SMP
                              Tue Feb 23 19:00:38 UTC 2016 x86_64 x86_64
Alert Count                   2
First Seen                    2016-02-26 18:51:28 CET
Last Seen                     2016-03-03 17:07:50 CET
Local ID                      ef95c681-dac9-415c-8f22-88fdf459be19

Raw Audit Messages
type=AVC msg=audit(1457021270.419:404): avc:  denied  { getattr } for  pid=885 comm="systemd-logind" path="/dev/shm/lldpad.state" dev="tmpfs" ino=8520 scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=0


Hash: systemd-logind,systemd_logind_t,tmpfs_t,file,getattr

*** Bug 1328784 has been marked as a duplicate of this bug. ***

*** Bug 1335653 has been marked as a duplicate of this bug. ***

I think something went wrong here in this bug report.

As far as I can tell, the SELinux issue is completely unrelated. Please report it separately.

@myfedora, @Andrey V. Henneberg: In case your bug report is related to the SELinux issue, please report it separately.


For the SIGSEGV crasher in yumex-dnf:
Can anyone please post steps to reproduce this issue? It looks like some weird race condition to me.

*** Bug 1343206 has been marked as a duplicate of this bug. ***

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.

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.