Actions
Bug #5493
closedSegfault in osmo-upf when running gtp-load-test
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/22/2022
Due date:
% Done:
0%
Spec Reference:
Description
I used osmo-pfcp-tool to setup an endecaps session with osmo-upf.
After starting gtp-load-test osmo-upf segfaults:
(gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007ffff698f473 in poll_disp_fds (n_fd=n_fd@entry=5) at select.c:361 #2 0x00007ffff698f573 in _osmo_select_main (polling=polling@entry=0) at select.c:399 #3 0x00007ffff698f6b9 in osmo_select_main_ctx (polling=polling@entry=0) at select.c:455 #4 0x000055555568aaac in main (argc=<optimized out>, argv=<optimized out>) at osmo_upf_main.c:345 (gdb) f 1 #1 0x00007ffff698f473 in poll_disp_fds (n_fd=n_fd@entry=5) at select.c:361 361 ufd->cb(ufd, flags); (gdb) p *ufd $4 = {list = {next = 0x616000004a70, prev = 0x6100000015a0}, fd = 7, when = 1, cb = 0x0, data = 0x0, priv_nr = 0}
I attached the config files I used to setup osmo-upf. gbp-load-gen was started with:
gtp-load-gen -g 1 -t 1 -f 1 -e 1 -l 127.0.0.12 -r 127.0.0.11 -s 10.11.0.2 -d 10.11.0.1
Note that the UE ips could be the wrong way around, but the segfault should still be fixed.
Files
Updated by neels about 2 years ago
I ran with these files and current osmo-upf branch neels/wip and can't reproduce the segfault.
Swapping IP addresses shouldn't really cause segfaults AFAICT.
Do you still see the segfault?
Updated by daniel about 2 years ago
- Status changed from New to Rejected
Thanks for checking. I used a non-current checkout of neels/upf - current neels/wip works for me.
Actions