-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes for timer expiry for stateless mme #1957
Fixes for timer expiry for stateless mme #1957
Conversation
Fixed the memory leaks for mme_app timers
…enb_s1ap_id_same_ue.py 2. With this fix basic attach-detach test case is passing on enabling stateles MME
…fferent_enb_s1ap_id_same_ue.py" This reverts commit f6658a0.
Can one of the admins verify this patch? |
during commit, have you included "-s" option for sign off? check out https://github.com/magma/community/blob/main/CONTRIBUTING.md |
In the summary, could you put more context, e.g., why the change is done in addition to what the change is? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes look good to me, but summary and sign off should be taken care of.
Signed-off-by: rashmi <rashmi.sarwad@radisys.com>
94b2940
to
de026d0
Compare
…_timer_expiry_for_stateless
…_timer_expiry_for_stateless Signed-off-by: rashmi <rashmi.sarwad@radisys.com>
Description:
Issue #1 : While testing the Implicit detach timer with MME restart observed that UE contexts were not updated to redis DB. Because on timer expiry, imsi64 was neither received from timer module nor got from the handler function. So imsi64 was set to "INVALID_IMSI64". Only for valid imsi64 values, UE contexts are updated to DB.
Approach followed to address above issue:
Issue #2: The prototype of timer start function is int timer_setup(
uint32_t interval_sec, uint32_t interval_us, task_id_t task_id,
int32_t instance, timer_type_t type, void* timer_arg, size_t arg_size,
long* timer_id)
Which expects seconds and micro-seconds to be of datatype uint32_t, but for most timers while calling timer_setup, seconds and micro-seconds were defined as long
Test Plan:
Executed s1ap tester sanity test suite