new timer code: semantics of osmo_timer_schedule for already scheduled timer

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/.

Sylvain Munaut 246tnt at gmail.com
Fri Nov 11 14:56:21 UTC 2011


Hi,

While updating libosmocore in osmocom-bb, a problem arised: 100%CPU
usage and hanging. Turns out 'mobile' sometimes call
osmo_timer_schedule for an already scheduled timer.

Obviously this used to work and now it doesn't. The question is : Was
there a defined semantics for this case previously ? Or is it supposed
to be unsupported ? What would you expect it to do ?

Cheers,

    Sylvain




More information about the OpenBSC mailing list