fixeria has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/42031?usp=email )
Change subject: doc: fix default 'max-initial' value
......................................................................
doc: fix default 'max-initial' value
The default value is set in gsm_bts_trx_alloc() and it's actually 0.
Change-Id: I178e0664f6818d0eda15701b57bb030916b06006
---
M doc/manuals/chapters/configuration.adoc
1 file changed, 1 insertion(+), 1 deletion(-)
Approvals:
Jenkins Builder: Verified
laforge: Looks good to me, but someone else must approve
pespin: Looks good to me, approved
diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc
index f6ca75e..ddaa113 100644
--- a/doc/manuals/chapters/configuration.adoc
+++ b/doc/manuals/chapters/configuration.adoc
@@ -197,7 +197,7 @@
configuration file.
De-activating power-ramping can be performed by setting the max-initial value
-to the nominal power. The default max-initial value is 23 dBm.
+to the nominal power. The default max-initial value is 0 dBm.
==== Running multiple instances
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42031?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: merged
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I178e0664f6818d0eda15701b57bb030916b06006
Gerrit-Change-Number: 42031
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/42010?usp=email )
Change subject: assignment_fsm: Fix use-after-free of lchan->conn
......................................................................
assignment_fsm: Fix use-after-free of lchan->conn
Scenario:
* A DYNAMIC/OSMOCOM TS in PDCH mode is selected to be used for TCH/F,
hence the TS is being switched to TCH/F: RF Channel Release is being
transmitted and waiting to receive RF Channel release ACK. Hence,
lchan is in state LCHAN_ST_WAIT_TS_READY, and there's a conn with an
assignment FSM pointing to it in conn->assignment.new_lchan.
lchan->conn also points to the related conn.
* The BSSMAP SCCP link goes down (link lost), which will terminate the
conn->fi of all conns related to the MSC peer going down.
During that teardown, first gscon_pre_term()->gscon_release_lchans()->
assignment_reset() is called, which sets
conn->assignment.new_lchan=NULL and calls lchan_release(). This path
leaves conn->assignment.new_lchan->conn untouched!
* Later in the call path, when finally the bsc_subscr is put() to 0
references and associated lchan gets its lchan_forget_conn() called,
it will access lchan->conn which was not freed in the previous step
mentioned above during assignment_reset().
This patch fixes the issue by adding a lchan_forget_conn() after the
lchan_release() in assignment_reset(), to make sure the conn is no
longer user by the lchan afterwards.
Related: OS#6936
Change-Id: Ifbb9a61cd8a40d953ef5c2b52f9be9ef0dffefa4
---
M src/osmo-bsc/assignment_fsm.c
1 file changed, 1 insertion(+), 0 deletions(-)
Approvals:
pespin: Looks good to me, approved
Jenkins Builder: Verified
fixeria: Looks good to me, but someone else must approve
laforge: Looks good to me, but someone else must approve
diff --git a/src/osmo-bsc/assignment_fsm.c b/src/osmo-bsc/assignment_fsm.c
index f0a2781..e5392f6 100644
--- a/src/osmo-bsc/assignment_fsm.c
+++ b/src/osmo-bsc/assignment_fsm.c
@@ -127,6 +127,7 @@
struct gsm_lchan *lchan = conn->assignment.new_lchan;
conn->assignment.new_lchan = NULL;
lchan_release(lchan, false, true, RSL_ERR_EQUIPMENT_FAIL, NULL);
+ lchan_forget_conn(lchan);
}
if (conn->assignment.created_ci_for_msc) {
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/42010?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: merged
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ifbb9a61cd8a40d953ef5c2b52f9be9ef0dffefa4
Gerrit-Change-Number: 42010
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Attention is currently required from: daniel, fixeria.
pespin has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-bsc/+/41993?usp=email )
Change subject: Lb: Handle N-PCSTATE.ind
......................................................................
Patch Set 2:
(1 comment)
File src/osmo-bsc/lb.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/41993/comment/fb45d842_fb627efa?usp… :
PS2, Line 147: /* Find an SMLC by its remote sigtran point code on a given cs7 instance. */
> Done
Yes, because so far we only support one smlc, but I thought it was good to leave this encapsulation in place since we have similar code to handle the A interface in osmo_bsc_sigtran, this way both can be modified similarly.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/41993?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I16900b9c2b840d4c7d8471c1f69b19601e892b2d
Gerrit-Change-Number: 41993
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: daniel <dwillmann(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 04 Feb 2026 17:01:04 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: daniel <dwillmann(a)sysmocom.de>