MSC subscriber conn FSM issues

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Mon Mar 19 01:00:38 UTC 2018


In recent weeks, many of you have encountered and worked at failures of
OsmoMSC's subscriber conn FSM / the conn itself to handle corner cases and/or
cleanly handle error situations.

I have plans for that FSM to be reviewed, adding probably two more states to
it, a) to properly handle the early startup and b) gracefully release in all
situations; and to probably more closely glue the conn struct to the FSM.

My humble suggestion is to wait for me to review it and not spend more time on
it until that is through. I wrote the FSM initially, and it makes sense that I
clarify its structuring before all of you need to learn its current quirks.

I hope it won't take too long, just need to sort the priorities of this fix
versus the other tasks I have...

~N

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180319/46dadf9a/attachment.bin>


More information about the OpenBSC mailing list