Change in osmo-bts[master]: rsl: NACK Chan Activation for lchans on disabled TS

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/gerrit-log@lists.osmocom.org/.

pespin gerrit-no-reply at lists.osmocom.org
Thu Oct 7 10:25:32 UTC 2021


pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/25702 )

Change subject: rsl: NACK Chan Activation for lchans on disabled TS
......................................................................

rsl: NACK Chan Activation for lchans on disabled TS

A broken BSC could send a Chan Activation on a TS which has not yet been
enabled (or even configured). This is the case with our TTCN3 tests,
where OML side is currently handled in parallel by an osmo-bsc while
TTCN3 takes care of the RSL side. This can actually be seen as a
malfunctioning BSC, but it was spotted that given this sequence of
events osmo-bts can crash (see ticket below).

Hence, let's NACK any attempt from a BSC to activate an lchan on a
disabled TS.

Related: OS#5249
Change-Id: I9c3b68487c12efc412a057728a561e061560c544
---
M src/common/rsl.c
1 file changed, 7 insertions(+), 0 deletions(-)

Approvals:
  Jenkins Builder: Verified
  fixeria: Looks good to me, approved



diff --git a/src/common/rsl.c b/src/common/rsl.c
index 507a7cf..c73b093 100644
--- a/src/common/rsl.c
+++ b/src/common/rsl.c
@@ -1633,6 +1633,13 @@
 		return rsl_tx_chan_act_nack(lchan, RSL_ERR_EQUIPMENT_FAIL);
 	}
 
+	if (ts->mo.nm_state.operational != NM_OPSTATE_ENABLED ||
+	    ts->mo.nm_state.availability != NM_AVSTATE_OK) {
+		LOGP(DRSL, LOGL_ERROR, "%s rx chan activ but TS not in nm_state oper=ENABLED avail=OK, nack!\n",
+		     gsm_ts_and_pchan_name(ts));
+		return rsl_tx_chan_act_nack(lchan, RSL_ERR_RR_UNAVAIL);
+	}
+
 	if (ts->pchan == GSM_PCHAN_OSMO_DYN) {
 		ts->dyn.pchan_want = dyn_pchan_from_chan_nr(dch->chan_nr);
 		DEBUGP(DRSL, "%s rx chan activ\n", gsm_ts_and_pchan_name(ts));

-- 
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/25702
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I9c3b68487c12efc412a057728a561e061560c544
Gerrit-Change-Number: 25702
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy at sysmocom.de>
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-MessageType: merged
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211007/88256a4f/attachment.htm>


More information about the gerrit-log mailing list