Attention is currently required from: neels, laforge.
keith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28342 )
Change subject: After RX of an SMPP Submit, send the SMS we just received.
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> Out of many things I could understand I may have miscommunicated, I can't see how I have suggested t […]
Uh.. reading this entire thread.. I've ended up write essays on gerrit recently 😞
I realise there's an incongruency. To be clear:
I do think it is better to try to deliver the SMS on receipt, that is to say: add it to the in memory "sms-queue", rather than just drop it into the database and wait/hope for the database getter to load it into the in-memory sms-queue.
The reason why I mentioned above that something "makes these patches unnecessary" is two-fold:
1) complete removal of sms-queue from osmo-msc. - much talked about at times, but I'm not holding my breath for it.
2) removal of the sqlite based storage which allows a more aggressive storage to in-memory queue getter, which somewhat mitigates the problem.
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28342
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I9af51ef0d9c2e6c5acc5128efd6195df881b680c
Gerrit-Change-Number: 28342
Gerrit-PatchSet: 2
Gerrit-Owner: keith <keith(a)rhizomatica.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 30 Jan 2023 18:38:21 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: keith <keith(a)rhizomatica.org>
Gerrit-MessageType: comment
Attention is currently required from: neels, laforge.
keith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28342 )
Change subject: After RX of an SMPP Submit, send the SMS we just received.
......................................................................
Patch Set 2:
(2 comments)
Patchset:
PS2:
> if this patch helps you in production setups, and it has been tested/verified there, please rebase a […]
Out of many things I could understand I may have miscommunicated, I can't see how I have suggested that it "hardly matters". I think that delivering a sent SMS as soon as possible is rather important. I think I explained why this isn't happening. It's also been observed at the congress event.
PS2:
> if this patch helps you in production setups, and it has been tested/verified there, please rebase a […]
This patch is actually part of a larger patch set that I am currently running in production setup. Some of the other patches had been submitted here, including
https://gerrit.osmocom.org/c/osmo-msc/+/28338/1 which was abandoned due to your valid comment there: "... It creates a merge nightmare for all of my work on a SQL-less SMS storage backend... "
The patch set that I am running, is not experiencing the bizarre, up to some minutes of duration stalls that we observed last year related to sqlite driver? or disk access/locking? or who knows what? - I remember well that after valiant attempts to figure out what was going on, the conclusion was something like: I don't care (anymore) what sqlite is doing, let's simply remove it, hence your sprint to implement file based storage for the SMS queue..
I do not know which patch(es) is/are avoiding the lockups, but I have a feeling it has to do with all or some of:
1) not rapidly doing UPDATE followed by DELETE operations.
2) implementing a timer to prevent successive queue runs (possibly giving the sqlite/disk IO or I don't know what a chance to "catch up"?
My hypothesis is that current master osmo-msc continues to suffer from this stalling problem and I think it will be observed if there is significant SMS traffic, at for example a CCC event. Therefore, I don't see much point in submitting this patch alone. - This patch simply addresses an issue that I noticed while doing a pretty intense analysis of the SMS queue. This issue would be relevant regardless of the actual storage backend, if the queue is large enough.
A possibility for me at this point is: rebase and resumbit all the patches relevant to sqlite based SMS-Q and rebase laforge/nosql on top of that work. I don't know how complicated that might be, but it could be a solution to not creating that work for somebody else by merging the sqlite work to master.
At the same time, I'm not necessarily happy with the sqlite work as I don't know EXACTLY why it alleviates the problem and I have -ENOTEXIST desire to push patches that I do not understand through CR, or to create more pending patches that sit like this one for six months.
Maybe worth also saying that dropping sqlite and switching to file based SMS storage also creates a work load for me in that I have to adapt code that I run to deal with that. Mostly, the routine that checks for SMS sitting in local queue for a destination that is currently attached to another VLR, (distributed-GSM-SMSQ if you like) But it's probably as simple as changing the db access routines to file access routines.
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28342
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I9af51ef0d9c2e6c5acc5128efd6195df881b680c
Gerrit-Change-Number: 28342
Gerrit-PatchSet: 2
Gerrit-Owner: keith <keith(a)rhizomatica.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 30 Jan 2023 18:29:29 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: keith <keith(a)rhizomatica.org>
Gerrit-MessageType: comment
Attention is currently required from: pespin, dexter.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31111 )
Change subject: pcu_sock: complain when not PDCH is available at all
......................................................................
Patch Set 1:
(2 comments)
Patchset:
PS1:
> I don't really see the point in printing that information, specially as NOTICE. […]
Agreeing with Pau here.
File src/osmo-bsc/pcu_sock.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/31111/comment/b6505260_24c55144
PS1, Line 165: found_pdch
no need for an additional variable, simply check if: trx_info->pdch_mask == 0.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31111
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ie3e5409cd798f6027404c0ff95297af850e516c4
Gerrit-Change-Number: 31111
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 18:28:51 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/31109 )
Change subject: trxcon: Fix heap-use-after-free in l1ctl_client
......................................................................
trxcon: Fix heap-use-after-free in l1ctl_client
If the peer connected to trxcon restarts the process, read() on the unix
socket in trxcon fails, and triggers closing the conn (l1ctl_client),
which ends up freeing the struct. This all happens during read_cb() of
the l1ctl_client wqueue. If the kernel also flags WRITE event in the
same main loop iteration, the wqueue code would end up using the freed
struct again when running the write_cb.
Make sure the read_cb returns -EBADF in the code branch closing the conn
in read_cb, since it makes no sense to handle a write_cb after that.
This saves the code from accessing the potentially freed struct.
Related: OS#5872
Change-Id: I100a8ba056a09b4e52675e3539640da0c0f8d837
---
M src/host/trxcon/src/l1ctl_server.c
1 file changed, 1 insertion(+), 1 deletion(-)
Approvals:
Jenkins Builder: Verified
fixeria: Looks good to me, approved
diff --git a/src/host/trxcon/src/l1ctl_server.c b/src/host/trxcon/src/l1ctl_server.c
index bfbd997..c0f1015 100644
--- a/src/host/trxcon/src/l1ctl_server.c
+++ b/src/host/trxcon/src/l1ctl_server.c
@@ -61,7 +61,7 @@
rc = -EIO;
}
l1ctl_client_conn_close(client);
- return rc;
+ return -EBADF; /* client fd is gone, avoid processing any other events. */
}
/* Check message length */
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/31109
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I100a8ba056a09b4e52675e3539640da0c0f8d837
Gerrit-Change-Number: 31109
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: merged
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31113 )
Change subject: pcuif_proto: add indication to communicate E1 parameters
......................................................................
Patch Set 1:
(4 comments)
Commit Message:
https://gerrit.osmocom.org/c/osmo-bsc/+/31113/comment/9b295746_0d1474b0
PS1, Line 10: setup. To avioud duplicate configuration the BSC has to communicate the
"avoid"
https://gerrit.osmocom.org/c/osmo-bsc/+/31113/comment/968f1de1_6913b767
PS1, Line 11: E1 parameters (which TS, SS etc.) to the PCU. Lets add a new primitive
What do you mean with "to avoid duplicate configuration" here? where would the duplicate configuration be? what would the other way be?
File include/osmocom/bsc/pcuif_proto.h:
https://gerrit.osmocom.org/c/osmo-bsc/+/31113/comment/914f87e2_5196a3c6
PS1, Line 263: uint8_t pdch_trx_no;
this was not yet changed to trx_nr, why?
https://gerrit.osmocom.org/c/osmo-bsc/+/31113/comment/7de699c2_f0b4dd12
PS1, Line 264: uint8_t pdch_ts;
this was not yet changed to ts_nr, why?
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31113
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ia7928489130c1205b06bb9b10de0fb1461843301
Gerrit-Change-Number: 31113
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 17:42:19 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31112 )
Change subject: timeslot_fsm: Warn in case Ercisson RBS uses static PDCH
......................................................................
Patch Set 1: Code-Review-1
(2 comments)
Commit Message:
https://gerrit.osmocom.org/c/osmo-bsc/+/31112/comment/d021fa43_acf0bea3
PS1, Line 13: actively manage the channel than. In the case of Ericsson we have to
"the channel than" I don't understand this part.
File src/osmo-bsc/timeslot_fsm.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/31112/comment/f9785853_647641b0
PS1, Line 343: case GSM_PCHAN_PDCH:
IIRC we have already a specific function checking the timeslot configuration restictions for each/all BTS. This code should go there imho, to prevent users from configuring channels as PDCH if BTS type is ericcsson.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31112
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icc7c2956fc934691e3bfacb283d896a8767baf27
Gerrit-Change-Number: 31112
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 17:38:38 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31111 )
Change subject: pcu_sock: complain when not PDCH is available at all
......................................................................
Patch Set 1: Code-Review-1
(3 comments)
Commit Message:
https://gerrit.osmocom.org/c/osmo-bsc/+/31111/comment/3afb7709_f9b8cbd1
PS1, Line 7: pcu_sock: complain when not PDCH is available at all
"no PDCH"
https://gerrit.osmocom.org/c/osmo-bsc/+/31111/comment/c8a619a5_65c8f331
PS1, Line 9: In case no PDCH is currently available (resources exhausted, or simple a
"simply"
Patchset:
PS1:
I don't really see the point in printing that information, specially as NOTICE. It can be totally fine to have a non-pdch non-gprs network.
If someone wants to find out about that kind of information, that message itself is not going to be enough, and anyway the user should go to look at VTY or logs in the PCU.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31111
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ie3e5409cd798f6027404c0ff95297af850e516c4
Gerrit-Change-Number: 31111
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 17:35:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31112 )
Change subject: timeslot_fsm: Warn in case Ercisson RBS uses static PDCH
......................................................................
timeslot_fsm: Warn in case Ercisson RBS uses static PDCH
The Ericsson RBS is a BTS that natively works with dynamic timeslots.
This colides with the current understanding of static PDCH channels
because the BTSs we support so far get thier static PDCH information on
startup and then handle everything related internally. The BSC does not
actively manage the channel than. In the case of Ericsson we have to
activate the PDCH via RSL like any other channel and the timeslot FSM
has to manage it. Lets not add work arouds for this, lets just print and
error message and use the BTS in the dynamic scheme as intended by the
manufacturer.
Change-Id: Icc7c2956fc934691e3bfacb283d896a8767baf27
Related: OS#5198
---
M src/osmo-bsc/timeslot_fsm.c
1 file changed, 17 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/12/31112/1
diff --git a/src/osmo-bsc/timeslot_fsm.c b/src/osmo-bsc/timeslot_fsm.c
index 72db0fa..fb1edd8 100644
--- a/src/osmo-bsc/timeslot_fsm.c
+++ b/src/osmo-bsc/timeslot_fsm.c
@@ -340,6 +340,23 @@
}
switch (ts->pchan_on_init) {
+ case GSM_PCHAN_PDCH:
+ /* NOTE: A static PDCH is usually handled by the BTS/PCU internally, the BSC
+ * will not actively manage this channel. It will just keep the timeslot
+ * unused so that it is free for the BTS/PCU to use it as PDCH. Not all BTSs
+ * work well in this scheme. Ericsson RBS BTSs support dynamic channels natively
+ * and require a channel activation on RSL level before the PDCH can be used.
+ * One could work around this by activating the PDCH once on startup and
+ * leave it on indefinetly but we decided not to do so. Users of Ericsson RBS
+ * BTSs must configure a dynamic PDCH channel. */
+ if (is_ericsson_bts(bts)) {
+ LOG_TS(ts, LOGL_ERROR, "Ericsson RBS does not support static PDCH, use TCH/F_TCH/H_SDCCH8_PDCH\n");
+ break;
+ }
+
+ /* nothing to do */
+ break;
+
case GSM_PCHAN_OSMO_DYN:
case GSM_PCHAN_TCH_F_PDCH:
if (bts->gprs.mode == BTS_GPRS_NONE) {
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31112
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icc7c2956fc934691e3bfacb283d896a8767baf27
Gerrit-Change-Number: 31112
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: newchange
dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31111 )
Change subject: pcu_sock: complain when not PDCH is available at all
......................................................................
pcu_sock: complain when not PDCH is available at all
In case no PDCH is currently available (resources exhausted, or simple a
bug that prevents TS to be recognized as usable for PDCH) display an
error message to inform the user about this.
Change-Id: Ie3e5409cd798f6027404c0ff95297af850e516c4
Related: OS#5198
---
M src/osmo-bsc/pcu_sock.c
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/11/31111/1
diff --git a/src/osmo-bsc/pcu_sock.c b/src/osmo-bsc/pcu_sock.c
index def2df0..e8e7109 100644
--- a/src/osmo-bsc/pcu_sock.c
+++ b/src/osmo-bsc/pcu_sock.c
@@ -123,6 +123,7 @@
{
unsigned int tn;
const struct gsm_bts_trx_ts *ts;
+ bool found_pdch = false;
trx_info->hlayer1 = 0x2342;
trx_info->pdch_mask = 0;
@@ -157,7 +158,12 @@
ts->hopping.hsn, ts->hopping.maio, trx_info->ts[tn].ma_bit_len);
else
LOGPC(DPCU, LOGL_INFO, "hopping=no arfcn=%u)\n", trx->arfcn);
+
+ found_pdch = true;
}
+
+ if (!found_pdch)
+ LOG_TRX(trx, DPCU, LOGL_NOTICE, "unavailable for PCU -- currently no TS available for PDCH\n");
}
/* Send BTS properties to the PCU */
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31111
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ie3e5409cd798f6027404c0ff95297af850e516c4
Gerrit-Change-Number: 31111
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: laforge, pespin, fixeria.
dexter has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/30876 )
Change subject: pcu_sock: rework check logic for ts
......................................................................
Patch Set 7:
(1 comment)
File src/osmo-bsc/pcu_sock.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/30876/comment/27cf6690_ed45c92b
PS2, Line 96: static bool ts_is_pdch(const struct gsm_bts_trx_ts *ts)
> osmocom-style dynamic TS are virtually identical to ericsson-style dynamic TS
When I understand this correctly, then pcu_tx_info_ind() should be run each time there is a change with the channel configuration. On the BTS side I see a call to pcu_tx_info_ind() from rsl_rx_chan_activ().
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/30876
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icaab52ab73c38889dfadb523b89bb54cafacc99a
Gerrit-Change-Number: 30876
Gerrit-PatchSet: 7
Gerrit-Owner: dexter <pmaier(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>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 17:28:55 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: laforge, pespin, fixeria.
Hello Jenkins Builder, laforge, pespin, fixeria,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-bsc/+/30876
to look at the new patch set (#7).
Change subject: pcu_sock: rework check logic for ts
......................................................................
pcu_sock: rework check logic for ts
Before filling in the TS in the info indication, it is checked that the
MO opstate is enabled. Also it is checked that the TS serves a PDCH.
Lets restructure this check and move the PDCH check into a helper
function as we need to check for PDCH from other location as well later.
Change-Id: Icaab52ab73c38889dfadb523b89bb54cafacc99a
Related: OS#5198
---
M src/osmo-bsc/pcu_sock.c
1 file changed, 17 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/76/30876/7
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/30876
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icaab52ab73c38889dfadb523b89bb54cafacc99a
Gerrit-Change-Number: 30876
Gerrit-PatchSet: 7
Gerrit-Owner: dexter <pmaier(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>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newpatchset
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmocom-bb/+/31109 )
Change subject: trxcon: Fix heap-use-after-free in l1ctl_client
......................................................................
trxcon: Fix heap-use-after-free in l1ctl_client
If the peer connected to trxcon restarts the process, read() on the unix
socket in trxcon fails, and triggers closing the conn (l1ctl_client),
which ends up freeing the struct. This all happens during read_cb() of
the l1ctl_client wqueue. If the kernel also flags WRITE event in the
same main loop iteration, the wqueue code would end up using the freed
struct again when running the write_cb.
Make sure the read_cb returns -EBADF in the code branch closing the conn
in read_cb, since it makes no sense to handle a write_cb after that.
This saves the code from accessing the potentially freed struct.
Related: OS#5872
Change-Id: I100a8ba056a09b4e52675e3539640da0c0f8d837
---
M src/host/trxcon/src/l1ctl_server.c
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmocom-bb refs/changes/09/31109/1
diff --git a/src/host/trxcon/src/l1ctl_server.c b/src/host/trxcon/src/l1ctl_server.c
index bfbd997..c0f1015 100644
--- a/src/host/trxcon/src/l1ctl_server.c
+++ b/src/host/trxcon/src/l1ctl_server.c
@@ -61,7 +61,7 @@
rc = -EIO;
}
l1ctl_client_conn_close(client);
- return rc;
+ return -EBADF; /* client fd is gone, avoid processing any other events. */
}
/* Check message length */
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/31109
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I100a8ba056a09b4e52675e3539640da0c0f8d837
Gerrit-Change-Number: 31109
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: pespin, fixeria.
Hello osmith, Jenkins Builder, fixeria,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098
to look at the new patch set (#4).
Change subject: rlcmac: Enqueue LLC PDUs based on RadioPriority and SAPI
......................................................................
rlcmac: Enqueue LLC PDUs based on RadioPriority and SAPI
llc_queue and codel code has been taken from osmo-pcu.git
6a5b1b1f3ef83f87a9df1d4511e22f59039e11ed and have been refactored to fit
in libosmo-gprs (removed llc_pdu structs, reworked struct types being
enqueued, etc.). Support for queues based on radio_prio has also been
added.
Related: OS#5500
Change-Id: Icdaa046fb6a71367f10beee16dcf9a5b7b61022e
---
M include/osmocom/gprs/rlcmac/Makefile.am
A include/osmocom/gprs/rlcmac/codel.h
A include/osmocom/gprs/rlcmac/gre.h
A include/osmocom/gprs/rlcmac/llc_queue.h
M include/osmocom/gprs/rlcmac/rlcmac.h
M include/osmocom/gprs/rlcmac/rlcmac_private.h
M src/rlcmac/Makefile.am
A src/rlcmac/codel.c
A src/rlcmac/gre.c
A src/rlcmac/llc_queue.c
M src/rlcmac/rlcmac.c
M src/rlcmac/rlcmac_prim.c
12 files changed, 716 insertions(+), 3 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-gprs refs/changes/98/31098/4
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/31098
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Icdaa046fb6a71367f10beee16dcf9a5b7b61022e
Gerrit-Change-Number: 31098
Gerrit-PatchSet: 4
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: pespin.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmocom-bb/+/31108
to look at the new patch set (#2).
Change subject: layer23: Support configuring GSMTAP through VTY in l23 apps.
......................................................................
layer23: Support configuring GSMTAP through VTY in l23 apps.
This allow all l23 apps supporting L23_OPT_VTY and L23_OPT_TAP to
dynamically configure gsmtap through a "gsmtap" VTY node:
gsmtap
gsmtap-remote-host 127.0.0.2
gsmtap-sapi bcch
gsmtap-sapi ccch
gsmtap-sapi rach
gsmtap-sapi agch
gsmtap-sapi pch
gsmtap-sapi sdcch
gsmtap-sapi tch/f
gsmtap-sapi tch/h
gsmtap-sapi pacch
gsmtap-sapi pdtch
gsmtap-sapi ptcch
gsmtap-sapi cbch
gsmtap-category gprs dl-unknown
gsmtap-category gprs dl-dummy
gsmtap-category gprs dl-ctrl
gsmtap-category gprs dl-data-gprs
gsmtap-category gprs dl-data-egprs
gsmtap-category gprs ul-unknown
gsmtap-category gprs ul-dummy
gsmtap-category gprs ul-ctrl
gsmtap-category gprs ul-data-gprs
gsmtap-category gprs ul-data-egprs
VTY cmd "gsmtap-sapi" enables/disables tapping on general channel types,
while "gsmtap-category" allows fine-grained selection of messages being
tapped within the enabled sapis which would tap those messages.
Change-Id: I2582a1633d37d350a7f4c2bb5e03793bdf46e839
---
M src/host/layer23/include/osmocom/bb/common/l23_app.h
M src/host/layer23/include/osmocom/bb/common/vty.h
M src/host/layer23/src/common/l1ctl.c
M src/host/layer23/src/common/main.c
M src/host/layer23/src/common/sim.c
M src/host/layer23/src/common/vty.c
M src/host/layer23/src/mobile/main.c
7 files changed, 314 insertions(+), 20 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmocom-bb refs/changes/08/31108/2
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/31108
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I2582a1633d37d350a7f4c2bb5e03793bdf46e839
Gerrit-Change-Number: 31108
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/31104 )
Change subject: vty: Fix typo in symbol name
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
Submitting myself with a +1 since it's trivial.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/31104
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ib33ffba348d6e9414eb904bfb7a2bd7ba2f55344
Gerrit-Change-Number: 31104
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 16:23:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/31104 )
Change subject: vty: Fix typo in symbol name
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/31104
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ib33ffba348d6e9414eb904bfb7a2bd7ba2f55344
Gerrit-Change-Number: 31104
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 16:23:35 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: msuraev.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/31036 )
Change subject: Add SI10 support
......................................................................
Patch Set 9:
(1 comment)
File include/osmocom/gsm/protocol/gsm_04_08.h:
https://gerrit.osmocom.org/c/libosmocore/+/31036/comment/80ee12ab_027e9682
PS9, Line 1144: #elif OSMO_IS_BIG_ENDIAN
> (and CI should complain about it, I'll look into why it doesn't run automatically.)
-> https://osmocom.org/issues/5884
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/31036
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3a5da543f083f31e873c67b5ec1b5a439187d8f3
Gerrit-Change-Number: 31036
Gerrit-PatchSet: 9
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 16:04:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: msuraev.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/31036 )
Change subject: Add SI10 support
......................................................................
Patch Set 9:
(1 comment)
File include/osmocom/gsm/protocol/gsm_04_08.h:
https://gerrit.osmocom.org/c/libosmocore/+/31036/comment/c00abee5_e26931df
PS9, Line 1144: #elif OSMO_IS_BIG_ENDIAN
this part needs to be generated with
$ contrib/struct_endianess.py
(and CI should complain about it, I'll look into why it doesn't run automatically.)
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/31036
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3a5da543f083f31e873c67b5ec1b5a439187d8f3
Gerrit-Change-Number: 31036
Gerrit-PatchSet: 9
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 15:54:36 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: fixeria, msuraev.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/31080 )
Change subject: SI: add missing header
......................................................................
Patch Set 3: Code-Review+1
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/libosmocore/+/31080/comment/0e0e5772_3e8d7fc4
PS3, Line 7: SI: add missing header
As Pau mentioned, the title of this patch is misleading:
> btw, this patch is not adding a missing header. It's adding a missing function declaration in an existing header.
Besides that: LGTM!
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/31080
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Ia7530e9c8a21f6f99f3aac7baea5cbb38763c4f3
Gerrit-Change-Number: 31080
Gerrit-PatchSet: 3
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 15:50:52 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/31104 )
Change subject: vty: Fix typo in symbol name
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/31104
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ib33ffba348d6e9414eb904bfb7a2bd7ba2f55344
Gerrit-Change-Number: 31104
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 15:47:14 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
msuraev has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/31105 )
Change subject: SI: add missing Message Type
......................................................................
Set Ready For Review
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/31105
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Id3b59638a3cf75c7105b1992094a4cc20855161d
Gerrit-Change-Number: 31105
Gerrit-PatchSet: 1
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Mon, 30 Jan 2023 13:46:55 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
osmith has submitted this change. ( https://gerrit.osmocom.org/c/docker-playground/+/31103 )
Change subject: FR testsuites: clean up all networks before start
......................................................................
FR testsuites: clean up all networks before start
Add a new network_clean_remove_all_ttcn3 function and use it in the fr
related testsuites to ensure no network is running before the test
starts. We just had the situation where the network link between
gtp0-deb10fr (where these testsuites run exclusively, and only one at a
time) and the jenkins host went down. And so the clean up trap
apparently did not run and starting a new test fails as the old network
still exists and has the network devices attached.
Related: OS#5802
Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
---
M jenkins-common.sh
M ttcn3-fr-test/jenkins.sh
M ttcn3-gbproxy-test-fr/jenkins.sh
M ttcn3-ns-test/jenkins-fr.sh
4 files changed, 32 insertions(+), 0 deletions(-)
Approvals:
laforge: Looks good to me, but someone else must approve
pespin: Looks good to me, but someone else must approve
osmith: Looks good to me, approved
Jenkins Builder: Verified
diff --git a/jenkins-common.sh b/jenkins-common.sh
index ef0a3fc..a607f9a 100644
--- a/jenkins-common.sh
+++ b/jenkins-common.sh
@@ -262,6 +262,35 @@
docker network remove $NET_NAME
}
+# Clean and remove all docker networks related to ttcn3 testing. This prevents
+# running testsuites in parallel, so usually we don't want this and rely on the
+# clean_up_trap to clean the network. But on e.g. gtp0-deb10fr this gets used
+# as we only run one testsuite at once and it has dahdi netdevices attached.
+# Due connection loss, it may not be cleaned up there and so another testsuite
+# cannot start.
+network_clean_remove_all_ttcn3() {
+ local networks
+ local i
+
+ networks="$(docker network ls --format '{{.Name}}' | grep ^ttcn3- || true)"
+
+ if [ -z "$networks" ]; then
+ return
+ fi
+
+ set +x
+ echo "Removing stale network and containers..."
+ set -x
+
+ for i in $networks; do
+ NET_NAME="$i"
+ network_clean
+ network_remove
+ done
+
+ unset NET_NAME
+}
+
network_replace_subnet_in_configs() {
set +x
diff --git a/ttcn3-fr-test/jenkins.sh b/ttcn3-fr-test/jenkins.sh
index 9122063..12e14a5 100755
--- a/ttcn3-fr-test/jenkins.sh
+++ b/ttcn3-fr-test/jenkins.sh
@@ -30,6 +30,7 @@
mkdir $VOL_BASE_DIR/unix
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
diff --git a/ttcn3-gbproxy-test-fr/jenkins.sh b/ttcn3-gbproxy-test-fr/jenkins.sh
index ab62bc1..1c53173 100755
--- a/ttcn3-gbproxy-test-fr/jenkins.sh
+++ b/ttcn3-gbproxy-test-fr/jenkins.sh
@@ -33,6 +33,7 @@
mkdir $VOL_BASE_DIR/unix
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
diff --git a/ttcn3-ns-test/jenkins-fr.sh b/ttcn3-ns-test/jenkins-fr.sh
index 3b609ab..b6af67f 100755
--- a/ttcn3-ns-test/jenkins-fr.sh
+++ b/ttcn3-ns-test/jenkins-fr.sh
@@ -29,6 +29,7 @@
mkdir $VOL_BASE_DIR/ns
cp fr/osmo-ns-dummy.cfg $VOL_BASE_DIR/ns/
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31103
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
Gerrit-Change-Number: 31103
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: merged
Attention is currently required from: laforge.
msuraev has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/31039 )
Change subject: Add SI10 support
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> do we have a related TTCN3 test that sends the SI10 to osmo-bts and verifies it actually appears on […]
No, not yet.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/31039
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I268ba716ded330a024a8f3c0d1bd2f28622cecab
Gerrit-Change-Number: 31039
Gerrit-PatchSet: 2
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 30 Jan 2023 13:14:28 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: osmith.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/31103 )
Change subject: FR testsuites: clean up all networks before start
......................................................................
Patch Set 2: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31103
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
Gerrit-Change-Number: 31103
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:57:44 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: osmith.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/31103 )
Change subject: FR testsuites: clean up all networks before start
......................................................................
Patch Set 2: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31103
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
Gerrit-Change-Number: 31103
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:51:05 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/docker-playground/+/31103
to look at the new patch set (#2).
Change subject: FR testsuites: clean up all networks before start
......................................................................
FR testsuites: clean up all networks before start
Add a new network_clean_remove_all_ttcn3 function and use it in the fr
related testsuites to ensure no network is running before the test
starts. We just had the situation where the network link between
gtp0-deb10fr (where these testsuites run exclusively, and only one at a
time) and the jenkins host went down. And so the clean up trap
apparently did not run and starting a new test fails as the old network
still exists and has the network devices attached.
Related: OS#5802
Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
---
M jenkins-common.sh
M ttcn3-fr-test/jenkins.sh
M ttcn3-gbproxy-test-fr/jenkins.sh
M ttcn3-ns-test/jenkins-fr.sh
4 files changed, 32 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/docker-playground refs/changes/03/31103/2
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31103
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
Gerrit-Change-Number: 31103
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-MessageType: newpatchset
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/docker-playground/+/31103 )
Change subject: FR testsuites: clean up all networks before start
......................................................................
FR testsuites: clean up all networks before start
Add a new network_clean_remove_all_ttcn3 function and use it in the fr
related testsuites to ensure no network is running before the test
starts. We just had the situation where the network link between
gtp0-deb10fr (where these testsuites run exclusively, and only one at a
time) and the jenkins host went down. And so the clean up trap
apparently did not run and starting a new test fails as the old network
still exists and has the network devices attached.
Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
---
M jenkins-common.sh
M ttcn3-fr-test/jenkins.sh
M ttcn3-gbproxy-test-fr/jenkins.sh
M ttcn3-ns-test/jenkins-fr.sh
4 files changed, 32 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/docker-playground refs/changes/03/31103/1
diff --git a/jenkins-common.sh b/jenkins-common.sh
index ef0a3fc..a607f9a 100644
--- a/jenkins-common.sh
+++ b/jenkins-common.sh
@@ -262,6 +262,35 @@
docker network remove $NET_NAME
}
+# Clean and remove all docker networks related to ttcn3 testing. This prevents
+# running testsuites in parallel, so usually we don't want this and rely on the
+# clean_up_trap to clean the network. But on e.g. gtp0-deb10fr this gets used
+# as we only run one testsuite at once and it has dahdi netdevices attached.
+# Due connection loss, it may not be cleaned up there and so another testsuite
+# cannot start.
+network_clean_remove_all_ttcn3() {
+ local networks
+ local i
+
+ networks="$(docker network ls --format '{{.Name}}' | grep ^ttcn3- || true)"
+
+ if [ -z "$networks" ]; then
+ return
+ fi
+
+ set +x
+ echo "Removing stale network and containers..."
+ set -x
+
+ for i in $networks; do
+ NET_NAME="$i"
+ network_clean
+ network_remove
+ done
+
+ unset NET_NAME
+}
+
network_replace_subnet_in_configs() {
set +x
diff --git a/ttcn3-fr-test/jenkins.sh b/ttcn3-fr-test/jenkins.sh
index 9122063..12e14a5 100755
--- a/ttcn3-fr-test/jenkins.sh
+++ b/ttcn3-fr-test/jenkins.sh
@@ -30,6 +30,7 @@
mkdir $VOL_BASE_DIR/unix
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
diff --git a/ttcn3-gbproxy-test-fr/jenkins.sh b/ttcn3-gbproxy-test-fr/jenkins.sh
index ab62bc1..1c53173 100755
--- a/ttcn3-gbproxy-test-fr/jenkins.sh
+++ b/ttcn3-gbproxy-test-fr/jenkins.sh
@@ -33,6 +33,7 @@
mkdir $VOL_BASE_DIR/unix
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
diff --git a/ttcn3-ns-test/jenkins-fr.sh b/ttcn3-ns-test/jenkins-fr.sh
index 3b609ab..b6af67f 100755
--- a/ttcn3-ns-test/jenkins-fr.sh
+++ b/ttcn3-ns-test/jenkins-fr.sh
@@ -29,6 +29,7 @@
mkdir $VOL_BASE_DIR/ns
cp fr/osmo-ns-dummy.cfg $VOL_BASE_DIR/ns/
+network_clean_remove_all_ttcn3
network_create
network_replace_subnet_in_configs
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31103
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77
Gerrit-Change-Number: 31103
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: pespin, fixeria.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-gprs/+/31098 )
Change subject: rlcmac: Enqueue LLC PDUs based on RadioPriority and SAPI
......................................................................
Patch Set 3:
(2 comments)
File src/rlcmac/gre.c:
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098/comment/8ce5f9b8_b58fa759
PS3, Line 72: /* TODO: here a new UL TBF will be created if not available yet */
> Yes, I'm adding code modules in a step-by-step way, so that it's not a final code bomb with 30 files […]
Makes sense to do it that way. Sometimes a TODO is kept unintentionally though, so that's why I keep asking about them.
File src/rlcmac/llc_queue.c:
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098/comment/34b92ffd_7332e537
PS3, Line 196: /* rate_ctr_inc(CTR_LLC_FRAME_DROPPED); */
> I left it there on purpose so that a potential counter can be identified quickly and added there in […]
Ack
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/31098
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Icdaa046fb6a71367f10beee16dcf9a5b7b61022e
Gerrit-Change-Number: 31098
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:36:33 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: dexter.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/31023 )
Change subject: pcu_l1_if: ignore frame numbers that exceed the valid range
......................................................................
Patch Set 2: Code-Review-1
(1 comment)
File src/pcu_l1_if.cpp:
https://gerrit.osmocom.org/c/osmo-pcu/+/31023/comment/668efdd7_021fa4a5
PS2, Line 627: if (rach_ind->fn > GSM_TDMA_HYPERFRAME - 1)
I would also use OSMO_UNLIKELY here.
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/31023
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: Ib0cf1738be07733c95fc6c459a8a7c4cb2eeef26
Gerrit-Change-Number: 31023
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:15:33 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/31102 )
Change subject: pcuif_proto: add indication to communicate E1 parameters
......................................................................
Patch Set 1:
(1 comment)
File include/osmocom/pcu/pcuif_proto.h:
https://gerrit.osmocom.org/c/osmo-pcu/+/31102/comment/87335f71_8cf069dd
PS1, Line 263: uint8_t pdch_trx_no;
we use trx_nr and ts_nr everywhere afaict, better use same names.
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/31102
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: Ia7928489130c1205b06bb9b10de0fb1461843301
Gerrit-Change-Number: 31102
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:11:36 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: osmith, fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-gprs/+/31098 )
Change subject: rlcmac: Enqueue LLC PDUs based on RadioPriority and SAPI
......................................................................
Patch Set 3:
(1 comment)
File src/rlcmac/llc_queue.c:
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098/comment/f9fb0069_1f341ace
PS3, Line 155: break;
> does this intentionally only break the inner loop?
Good catch, this is wrong :) that's because I added an extra axis of priorities and updated the code but didn't see what you mention. I'll fix it.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/31098
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Icdaa046fb6a71367f10beee16dcf9a5b7b61022e
Gerrit-Change-Number: 31098
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:08:08 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: osmith, fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-gprs/+/31098 )
Change subject: rlcmac: Enqueue LLC PDUs based on RadioPriority and SAPI
......................................................................
Patch Set 3:
(2 comments)
File src/rlcmac/gre.c:
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098/comment/a0cf1290_1a001789
PS3, Line 72: /* TODO: here a new UL TBF will be created if not available yet */
> I guess you kept this on purpose?
Yes, I'm adding code modules in a step-by-step way, so that it's not a final code bomb with 30 files and 50k lines which will be impossible to review.
File src/rlcmac/llc_queue.c:
https://gerrit.osmocom.org/c/libosmo-gprs/+/31098/comment/30042095_1b7a4e2a
PS3, Line 196: /* rate_ctr_inc(CTR_LLC_FRAME_DROPPED); */
> commented out code. […]
I left it there on purpose so that a potential counter can be identified quickly and added there in the future.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/31098
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Icdaa046fb6a71367f10beee16dcf9a5b7b61022e
Gerrit-Change-Number: 31098
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 30 Jan 2023 12:06:56 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: comment