diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-03-24 05:43:04 +0100 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2019-04-11 05:36:36 +0000 |
| commit | d28aa0c2f1fc8827ee7f6958ab8d13630b9d2be9 (patch) | |
| tree | 9dd2fdb0f632ac212a6c97dc2aade58ef7e08f72 /src | |
| parent | 1f9cc018618e7d1e9a7a37e1ef08e059a4e02e87 (diff) | |
fsm_dealloc_test: no need for ST_DESTROYING
A separate ST_DESTROYING state originally helped with certain deallocation
scenarios. But now that fsm.c avoids re-entering osmo_fsm_inst_term() twice and
gracefully handles FSM instance deallocations for termination cascades, it is
actually just as safe without a separate ST_DESTROYING state. ST_DESTROYING was
used to flag deallocation and prevent entering osmo_fsm_inst_term() twice,
which works only in a very limited range of scenarios.
Remove ST_DESTROYING from fsm_dealloc_test.c to show that all tested scenarios
still clean up gracefully.
Change-Id: I05354e6cad9b82ba474fa50ffd41d481b3c697b4
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions