mme crashed when uplinkNASTransport EMM status following context setup response

[lezixiao]

mme crashed when uplinkNASTransport EMM status following context setup response.

1. after receiving EMM status in emm_state_initial_context_setup() status, mme deleted the gtp session.
2. after receiving contexte setup response, mme crashed for s1ap_handle_initial_context_setup_response: Assertion `sess' failed. (s1ap_handler.c:506)

I attached mme.log and wireshark log.
ENB-UE-S1AP-ID: 561
MME-UE-S1AP-ID: 566
IMSI: 311980000000726
MME_S11_TEID[113] SGW_S11_TEID[17]
[New LWP 13668]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `./nextepc-mmed -l ../var/log/nextepc/mme.log'.
Program terminated with signal 6, Aborted.
#0 0x00007f948c792207 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-gssapi-2.1.26-23.el7.x86_64 cyrus-sasl-lib-2.1.26-23.el7.x86_64 cyrus-sasl-md5-2.1.26-23.el7.x86_64 cyrus-sasl-plain-2.1.26-23.el7.x86_64 cyrus-sasl-scram-2.1.26-23.el7.x86_64 glibc-2.17-260.el7_6.5.x86_64 gmp-6.0.0-15.el7.x86_64 gnutls-3.3.29-9.el7_6.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_6.x86_64 libbson-1.3.5-6.el7.x86_64 libcom_err-1.42.9-13.el7.x86_64 libdb-5.3.21-24.el7.x86_64 libffi-3.0.13-18.el7.x86_64 libgcc-4.8.5-36.el7_6.2.x86_64 libgcrypt-1.5.3-14.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 libidn-1.28-4.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libtasn1-4.10-1.el7.x86_64 libyaml-0.1.4-11.el7_0.x86_64 lksctp-tools-1.0.17-2.el7.x86_64 mongo-c-driver-libs-1.3.6-1.el7.x86_64 nettle-2.7.1-8.el7.x86_64 nss-softokn-freebl-3.34.0-2.el7.x86_64 openssl-libs-1.0.2k-16.el7_6.1.x86_64 p11-kit-0.23.5-3.el7.x86_64 pcre-8.32-17.el7.x86_64 zlib-1.2.7-18.el7.x86_64
(gdb) bt
#0 0x00007f948c792207 in raise () from /lib64/libc.so.6
#1 0x00007f948c7938f8 in abort () from /lib64/libc.so.6
#2 0x00007f948d288245 in ogs_abort () at ogs-abort.c:31
#3 0x000000000042c279 in s1ap_handle_initial_context_setup_response (enb=0x255a2f0, message=0x7f9425ff9160) at s1ap_handler.c:506
#4 0x000000000043bfc5 in s1ap_state_operational (s=0x255a2f0, e=0x7f9489994998) at s1ap_sm.c:151
#5 0x00007f948d29bd8b in ogs_fsm_dispatch (sm=0x255a2f0, event=0x7f9489994998) at ogs-fsm.c:62
#6 0x0000000000417791 in mme_state_operational (s=0x7f9425ffad90, e=0x7f9489994998) at mme_sm.c:197
#7 0x00007f948d29bd8b in ogs_fsm_dispatch (sm=0x7f9425ffad90, event=0x7f9489994998) at ogs-fsm.c:62
#8 0x00000000004166e8 in mme_main (data=0x0) at mme_init.c:101
#9 0x00007f948d29250c in thread_worker (arg=0x7f94898c7718) at ogs-thread.c:67
#10 0x00007f948cb30dd5 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f948c859ead in clone () from /lib64/libc.so.6
(gdb)

mmeAndWireshark.tar.gz

[acetcom]

Nice catch! I've fixed that Initial Context Setup Response is ignored in this situation.

Thanks a lot!

[lezixiao]

thanks