Re: [Openlte-discuss] User deleted twice when NAS Attach Reject sended

[Ben W. <bwo...@gm...>]

Mikhail,

Thanks for pointing out the incorrect user delete logic.  I changed this
substantially, so that the user is now only deleted when the C-RNTI timer
(which is now only managed by the user manager) expires.  I think this will
address the different cases that you mention.  This will show up in the
next release.

Thanks,
Ben

On Mon, Aug 10, 2015 at 9:18 AM, Mikhail Gudkov <gm...@gm...> wrote:

> I think the user entity deleted (or can be deleted) twice
> when LTE_fdd_enb_mme send Attach Reject message.
>
> First delete in LTE_fdd_enb_mme line 1197
>
>     case LTE_FDD_ENB_MME_STATE_REJECT:
>         user_mgr->del_user(user, true); // <- delayed delete
>         send_attach_reject(user, rb);
>         break;
>
> Second delete can be found deeper in callstack:
>
>     send_attach_reject -> send_rrc_command -> start_c_rnti_release_timer.
>
> Last function starts another delayed operation. File LTE_fdd_enb_user_mgr
> line 179
>
>         // Initialize or delete the user
>         if((*iter).second->is_id_set())
>         {
>             (*iter).second->init();
>         }else{
>             del_user((*iter).second, false);
>         }
>
> There several cases like delete-init, delete-delete or init-delete can be
> occurred.
>
> Sorry for my English.
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Openlte-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlte-discuss
>
>