race in GTP configuration
Two threads access the variable: RC.gtpv1u_data_g->enb_port_for_S1u_S12_S4_up No explicit synchronization manages the write by "enb_app" thread and usage by "gtpu-v1" thread. So, the gtpu-v1 thread can read a wrong value of the MME address
New itti implementation made this case worse: the memory allocation of the whole structure RC.gtpv1u_data_g creation was implicitly protected by itti_mark_ready(), but now even the allocation is not protected. So it can reach a SEGV (because the pointer is NULL).
I suggest to fix this issue by implementing a explicit itti message from enb_app to gttpu-v1 thread within the configuration data (instead of writing directly in the global variable with no mutex).
If it's ok, i can do the fix this week