Bug #1995
closedSegfault when callin osmo_sccp_tx_unitdata() without being connected
100%
Description
The problem occurs when a peer (server role) tries to send unitdata to a remote peer (client) that is not connected.
The attached code contains the source code snippets I used for experimentation.
Good case:
fist start dummy_msc (client), then dummy_bsc (server). The client will connect and when the timer at the server expires unitdata is sent from the server to the client.
Bad case:
start dummy_bsc, when the timer expires, the segfault occurs.
Note: The scheme is a bit odd and not covered by the examples, since there, the server never actively sends data without being stimulated through an existing connection. It is questionable if a server should send unsolicited data at all. In this test, the server role has been chosen for one side because of the lack of an STP.
Files
Updated by laforge almost 7 years ago
- File 0001-osmo_ss7-Fix-segfault-when-routing-MTP-TRANSFER.req-.patch 0001-osmo_ss7-Fix-segfault-when-routing-MTP-TRANSFER.req-.patch added
- Status changed from New to In Progress
- % Done changed from 0 to 80
please see attached patch, it fixes the issue.
Updated by laforge almost 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
has been merged to master.