Attention is currently required from: fixeria.
Timur Davydov has posted comments on this change by Timur Davydov. ( https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email )
Change subject: proto_trxd: add helpers to prepare burst indication packets
......................................................................
Patch Set 2:
(1 comment)
File Transceiver52M/proto_trxd.h:
https://gerrit.osmocom.org/c/osmo-trx/+/42357/comment/2f7050b7_80b44481?usp… :
PS2, Line 39: trxd_prepare_burst_ind_v0
> This will be used in the following commits. […]
Done
--
To view, visit https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: Ie94a1df4879cbf6056cd05c9621c46db1ed972fd
Gerrit-Change-Number: 42357
Gerrit-PatchSet: 2
Gerrit-Owner: Timur Davydov <dtv.comp(a)gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Sat, 14 Mar 2026 06:34:00 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Comment-In-Reply-To: Timur Davydov <dtv.comp(a)gmail.com>
Attention is currently required from: fixeria.
Timur Davydov has posted comments on this change by Timur Davydov. ( https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email )
Change subject: proto_trxd: add helpers to prepare burst indication packets
......................................................................
Patch Set 2:
(1 comment)
File Transceiver52M/proto_trxd.h:
https://gerrit.osmocom.org/c/osmo-trx/+/42357/comment/8529860b_b38f5a1c?usp… :
PS2, Line 39: trxd_prepare_burst_ind_v0
> Why exposing this API? Is it used anywhere else outside of proto_trxd. […]
This will be used in the following commits. In the WebUSB-based setup the bursts will not be sent via a socket. Instead, the TRXD packet is prepared and passed through a callback to the web frontend, which then forwards it to the SDR device via WebUSB for transmission over RF.
--
To view, visit https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: Ie94a1df4879cbf6056cd05c9621c46db1ed972fd
Gerrit-Change-Number: 42357
Gerrit-PatchSet: 2
Gerrit-Owner: Timur Davydov <dtv.comp(a)gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 13 Mar 2026 22:51:30 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: Timur Davydov.
fixeria has posted comments on this change by Timur Davydov. ( https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email )
Change subject: proto_trxd: add helpers to prepare burst indication packets
......................................................................
Patch Set 2:
(1 comment)
File Transceiver52M/proto_trxd.h:
https://gerrit.osmocom.org/c/osmo-trx/+/42357/comment/a400e269_240d3843?usp… :
PS2, Line 39: trxd_prepare_burst_ind_v0
Why exposing this API? Is it used anywhere else outside of proto_trxd.c?
--
To view, visit https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: Ie94a1df4879cbf6056cd05c9621c46db1ed972fd
Gerrit-Change-Number: 42357
Gerrit-PatchSet: 2
Gerrit-Owner: Timur Davydov <dtv.comp(a)gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: Timur Davydov <dtv.comp(a)gmail.com>
Gerrit-Comment-Date: Fri, 13 Mar 2026 21:16:53 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Attention is currently required from: Timur Davydov.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified-1 by Jenkins Builder
Change subject: proto_trxd: add helpers to prepare burst indication packets
......................................................................
proto_trxd: add helpers to prepare burst indication packets
- introduce trxd_prepare_burst_ind_v0() and trxd_prepare_burst_ind_v1()
- reuse prepared packet size in send helpers
- handle idle frames during packet preparation
- use ssize_t consistently for prepared/write sizes
Change-Id: Ie94a1df4879cbf6056cd05c9621c46db1ed972fd
---
M Transceiver52M/proto_trxd.c
M Transceiver52M/proto_trxd.h
2 files changed, 62 insertions(+), 20 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-trx refs/changes/57/42357/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-trx/+/42357?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: Ie94a1df4879cbf6056cd05c9621c46db1ed972fd
Gerrit-Change-Number: 42357
Gerrit-PatchSet: 2
Gerrit-Owner: Timur Davydov <dtv.comp(a)gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: Timur Davydov <dtv.comp(a)gmail.com>
fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42356?usp=email )
Change subject: enb_proxy: fix stale SCTP events misprocessed during MME pool selection
......................................................................
enb_proxy: fix stale SCTP events misprocessed during MME pool selection
When closing a connection to one MME and opening a new one to the next,
a SHUTDOWN_COMP event from the old (now-closed) socket can still be
pending in the process mailbox. The sctp_assoc_change handlers in the
'connecting' and 'wait_s1setup_rsp' states were matching '_Socket',
ignoring the socket identity. A stale SHUTDOWN_COMP would therefore
fall into the '_ -> repeat_state_and_data' branch, triggering a spurious
re-entry of 'connecting', which immediately closed the newly established
connection to the next MME and skipped to yet another pool entry.
Fix this by matching the Socket against the current S#state.sock in both
handlers. Events arriving on a previously closed socket no longer match
these clauses and are silently dropped by the catch-all handle_event/4.
This was found thanks to the MME pooling TCs in ttcn3-s1gw-test.
Change-Id: I4211dd343607f045cf4dd33fa568ed580c79dd9f
Related: SYS#7052
---
M src/enb_proxy.erl
1 file changed, 8 insertions(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/erlang/osmo-s1gw refs/changes/56/42356/1
diff --git a/src/enb_proxy.erl b/src/enb_proxy.erl
index 5ab79d1..3ce205f 100644
--- a/src/enb_proxy.erl
+++ b/src/enb_proxy.erl
@@ -235,9 +235,11 @@
keep_state_and_data;
%% Handle an #sctp_assoc_change event (connection state)
-connecting(info, {sctp, _Socket, MmeAddr, MmePort,
+%% Match on Socket to avoid processing stale events from a previously closed socket
+connecting(info, {sctp, Socket, MmeAddr, MmePort,
{[], #sctp_assoc_change{state = ConnState,
- assoc_id = Aid}}}, S) ->
+ assoc_id = Aid}}},
+ #state{sock = Socket} = S) ->
MmeName = hd(S#state.tried_mmes),
case ConnState of
comm_up ->
@@ -315,9 +317,11 @@
%% Handle an #sctp_assoc_change event (MME connection state)
%% We may loose connection while waiting for the S1 SETUP RESPONSE
-wait_s1setup_rsp(info, {sctp, _Socket, MmeAddr, MmePort,
+%% Match on Socket to avoid processing stale events from a previously closed socket
+wait_s1setup_rsp(info, {sctp, Socket, MmeAddr, MmePort,
{[], #sctp_assoc_change{state = ConnState,
- assoc_id = Aid}}}, S) ->
+ assoc_id = Aid}}},
+ #state{sock = Socket} = S) ->
case ConnState of
comm_up ->
?LOG_NOTICE("MME connection (id=~p, ~p:~p) is already established?!?",
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42356?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: erlang/osmo-s1gw
Gerrit-Branch: master
Gerrit-Change-Id: I4211dd343607f045cf4dd33fa568ed580c79dd9f
Gerrit-Change-Number: 42356
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: laforge, osmith.
Hoernchen has posted comments on this change by Hoernchen. ( https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330?usp=email )
Change subject: fw source: force reformat once and for all
......................................................................
Patch Set 2:
(8 comments)
Patchset:
PS1:
> The approach I've taken with checkpatch (from linux. […]
clang-format formats and that is the end of it, no discussions, NOTHING EVER AGAIN.
That is the advantage and the reason why everyone uses a clang format file and why even the kernel has one, for the style we allegedly use, but clearly, we don't do that, and therefore we can didscuss formatting again and again and again...
File ccid_common/ccid_device.c:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/39b5d33c_b9… :
PS1, Line 547: // break;
> not useful IMHO. this is also in other places in this patch.
yeah but consistent and enforcable and easy to unindent after uncommenting the block.
File ccid_common/ccid_proto.h:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/c171a0bb_89… :
PS1, Line 366: #define CCID_CMD_STATUS_TIME_EXT 0x80
> here and in enum ccid_error_code below, it is more readable to keep the values directly below each o […]
looks more aligned now
File ccid_common/ccid_proto.c:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/23f69532_6e… :
PS1, Line 70: { CCID_ERR_CMD_ABORTED, "CMD_ABORTED" },
> +1
this is the alignment of arrays of structs. its either left, right, or one long line that breaks at 120 chars. neither left nor right is more or less readable than the randomly indented version and an random long line is obviously even worse, but at least this is consistent and can be applied and checked.
File ccid_common/iso7816_3.c:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/0781494e_2d… :
PS1, Line 50: 0,
> doesn't seem useful to reformat it like this?
it is definitely more readable than a sneaky semicolon at the end, and it's the kernel style we allegedly use...
File ccid_common/iso7816_fsm.c:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/f73fce2c_be… :
PS1, Line 168: static const uint8_t convention_convert_lut[256] = {
> yeah, that looks like it's not intended.
fixed by telling clang-format to keep it like that
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/0546c4f8_84… :
PS1, Line 818: .in_event_mask = S(ISO7816_E_RX_SINGLE) | S(ISO7816_E_RX_COMPL) | S(ISO7816_E_TX_COMPL) | S(ISO7816_E_RX_ERR_IND) | S(ISO7816_E_TX_ERR_IND) | S(ISO7816_E_TPDU_DONE_IND),
> https://gerrit.osmocom. […]
fixed by telling clang-format to keep it like this
File sysmoOCTSIM/usb_descriptors.c:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330/comment/eb879bb2_28… :
PS1, Line 227: 4,
> this also clearly is not an improvement of readability at all.
Done
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42330?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: Iacc086bb566551225e7a21b639a1ad2ec257484f
Gerrit-Change-Number: 42330
Gerrit-PatchSet: 2
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-CC: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Fri, 13 Mar 2026 19:37:32 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Comment-In-Reply-To: Hoernchen <ewild(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>