Actions
Bug #5192
closedns2: Creating a bind on a live system causes SEGV
Start date:
07/02/2021
Due date:
% Done:
100%
Spec Reference:
Description
Two FR binds were already configured and active inside an NSE. After that configuring another FR bind causes a segfault:
telnet localhost 4246 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmoGbProxy VTY interface Copyright (C) 2010 Harald Welte and On-Waves License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. OsmoGbProxy> enable OsmoGbProxy# configure terminal OsmoGbProxy(config)# ns OsmoGbProxy(config-ns)# bind fr hdlc3 OsmoGbProxy(config-ns-bind)# fr hdlc3 frnet OsmoGbProxy(config-ns-bind)# Connection closed by foreign host.
Jul 02 16:37:33 osmo-gbproxy[11564]: Fri Jul 2 16:37:33 2021 DLNS frame_relay.c:950 hdlc3: Creating frame relay link with role NETWORK Jul 02 16:37:33 osmo-gbproxy[11564]: Fri Jul 2 16:37:33 2021 DLNS gprs_ns2_fr.c:742 BIND(hdlc3) hdlc3: has correct frame relay mode and lmi Jul 02 16:37:33 osmo-gbproxy[11564]: Fri Jul 2 16:37:33 2021 DLNS gprs_ns2_fr.c:608 BIND(hdlc1) MTU changed from 1698 to 1700. Jul 02 16:37:33 osmo-gbproxy[11564]: Jul 02 16:37:33 systemd[1]: osmo-gbproxy.service: Main process exited, code=killed, status=11/SEGV Jul 02 16:37:33 systemd[1]: osmo-gbproxy.service: Failed with result 'signal'. Jul 02 16:37:35 systemd[1]: osmo-gbproxy.service: Service RestartSec=2s expired, scheduling restart. Jul 02 16:37:35 systemd[1]: osmo-gbproxy.service: Scheduled restart job, restart counter is at 2.
I wasn't able to reproduce it with a dead NSE yet
Actions