Attention is currently required from: pespin.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-gprs/+/32580 )
Change subject: gmm: Rework sess_id to identify one GMME
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/32580
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Ib757f016824d918ce8b74ae0c2a652a6c1823556
Gerrit-Change-Number: 32580
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 04 May 2023 00:16:16 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin, dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/32579 )
Change subject: select: speed up osmo_fd_is_registered
......................................................................
Patch Set 1: Code-Review-1
(1 comment)
Patchset:
PS1:
> You cannot guarantee that a correct pointer won't be LLIST_POISON1.
unfortunately not with its current value. If the LLIST_POISON1 value ended at an odd address, we could make the assumption, given that a pointer to a llist_head should never be pointing to an odd address.
But unfortunately 0x00100100 is very nicely aligned for 32/64bit and even larger alignments. So we could indeed end up seeing that address in the wild.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32579
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I1ce894da39e3f2329c88666a5dda594b8bce4228
Gerrit-Change-Number: 32579
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 04 May 2023 00:14:10 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/32597 )
Change subject: layer23: Store and use SAPI & NSAPI in apn->pdp
......................................................................
Patch Set 1:
(1 comment)
File src/host/layer23/src/modem/sndcp.c:
https://gerrit.osmocom.org/c/osmocom-bb/+/32597/comment/f0f313c7_adaa3d16
PS1, Line 183: uint32_t tlli = 0xe1c5d364;
> I still need to find out how to identify a given MS in the SN SAP of SNDCP. […]
I think I can retrieve it in the hook/forward of SNSM-ACTIVATE.ind/cnf in sndcp.c
In there I get NSAPI, SAPI, and TLLI, check 3GPP TS 44.065.
our libosmo-gprs-sm seems to be wrong and passing PTMSI instead:
gprs_sm_submit_snsm_act_ind() {
...
sndcp_prim_tx = osmo_gprs_sndcp_prim_alloc_snsm_activate_ind(
sme->ms->gmm.ptmsi,
sme->nsapi,
sme->llc_sapi);
...
}
Actually the whole SM layer seems to still use PTMSI vs TLLI the wrong way?
"""
struct gprs_sm_ms *gprs_sm_find_ms_by_tlli(uint32_t tlli)
{
struct gprs_sm_ms *ms;
llist_for_each_entry(ms, &g_sm_ctx->ms_list, list) {
if (ms->gmm.ptmsi == tlli)
return ms;
}
return NULL;
}
"""
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/32597
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: If82c94ca9c84a94e63a9a5d642a27a7b4e3ff089
Gerrit-Change-Number: 32597
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Wed, 03 May 2023 19:21:09 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/32597 )
Change subject: layer23: Store and use SAPI & NSAPI in apn->pdp
......................................................................
Patch Set 1:
(1 comment)
File src/host/layer23/src/modem/sndcp.c:
https://gerrit.osmocom.org/c/osmocom-bb/+/32597/comment/1c234380_e0669e15
PS1, Line 183: uint32_t tlli = 0xe1c5d364;
I still need to find out how to identify a given MS in the SN SAP of SNDCP. I cannot find anywhere where the app gets information about the current TLLI in use. Maybe I need to update some primitive to provide it at GMM/SM/SNDCP level.
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/32597
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: If82c94ca9c84a94e63a9a5d642a27a7b4e3ff089
Gerrit-Change-Number: 32597
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Wed, 03 May 2023 19:13:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment