Attention is currently required from: fixeria, tnt.
pespin has posted comments on this change. (
https://gerrit.osmocom.org/c/osmo-sgsn/+/36699?usp=email )
Change subject: gmm: mmctx_timer_stop(): warn about timer not running
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Patchset:
PS1:
Why does it happen at all ? […]
This in general
just means there's no timer set but anyway some code path is stopping it *just in case
any of those timers is enabled*.
It's actually not a good behavior overall, but I'd treat this as a shortcoming of
bad osmo-sgsn code architecture so far. I don't think it's easier to fix it easily
right now.
Since this commit improves the logging I'm fine with it.
--
To view, visit
https://gerrit.osmocom.org/c/osmo-sgsn/+/36699?usp=email
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-sgsn
Gerrit-Branch: master
Gerrit-Change-Id: I56ecad9d8f1049974b0896f6d0e7fc61580155ec
Gerrit-Change-Number: 36699
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: tnt <tnt(a)246tNt.com>
Gerrit-Attention: tnt <tnt(a)246tNt.com>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Sun, 05 May 2024 09:13:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: tnt <tnt(a)246tNt.com>
Gerrit-MessageType: comment