Version-Release number of selected component: samba-4.2.2-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/sbin/smbd crash_function: dump_core executable: /usr/sbin/smbd global_pid: 6236 kernel: 4.1.2-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 dump_core at ../source3/lib/dumpcore.c:337 #3 smb_panic_s3 at ../source3/lib/util.c:811 #4 smb_panic at ../lib/util/fault.c:166 #5 fault_report at ../lib/util/fault.c:83 #6 sig_fault at ../lib/util/fault.c:94 #8 file_close_user at ../source3/smbd/files.c:250 #9 smbXsrv_session_logoff at ../source3/smbd/smbXsrv_session.c:1583 #10 smbXsrv_session_clear_and_logoff at ../source3/smbd/smbXsrv_session.c:1118 #11 smbXsrv_session_destructor at ../source3/smbd/smbXsrv_session.c:1126 #12 _talloc_free_internal at ../talloc.c:993 Potential duplicate: bug 893121
Created attachment 1058231 [details] File: backtrace
Created attachment 1058232 [details] File: cgroup
Created attachment 1058233 [details] File: core_backtrace
Created attachment 1058234 [details] File: dso_list
Created attachment 1058235 [details] File: environ
Created attachment 1058236 [details] File: limits
Created attachment 1058237 [details] File: maps
Created attachment 1058238 [details] File: mountinfo
Created attachment 1058239 [details] File: namespaces
Created attachment 1058240 [details] File: open_fds
Created attachment 1058241 [details] File: proc_pid_status
Created attachment 1058242 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.