Change in libosmocore[master]: fsm_dealloc_test: no need for ST_DESTROYING

Neels Hofmeyr gerrit-no-reply at lists.osmocom.org
Mon Apr 8 00:59:23 UTC 2019


Hello Harald Welte, Jenkins Builder, 

I'd like you to reexamine a change. Please visit

    https://gerrit.osmocom.org/13393

to look at the new patch set (#6).

Change subject: fsm_dealloc_test: no need for ST_DESTROYING
......................................................................

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
---
M tests/fsm/fsm_dealloc_test.c
M tests/fsm/fsm_dealloc_test.err
2 files changed, 1,522 insertions(+), 1,801 deletions(-)


  git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/93/13393/6
-- 
To view, visit https://gerrit.osmocom.org/13393
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I05354e6cad9b82ba474fa50ffd41d481b3c697b4
Gerrit-Change-Number: 13393
Gerrit-PatchSet: 6
Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder (1000002)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190408/120a52ae/attachment.html>


More information about the gerrit-log mailing list