Attention is currently required from: pespin, msuraev.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/28892 )
Change subject: BSSMAP: make sure we don't try to reset non-existent entity
......................................................................
Patch Set 2: Code-Review-1
(3 comments)
Patchset:
PS2:
in OS#5551 i explain why this fix seems to be not needed.
If there is ever a situation where bssmap_reset == NULL,
we need to find that and fix it.
I currently don't see how that is possible at all.
There is not even uncertainty, race or async things going on, it is simply not possible.
File src/osmo-bsc/bsc_vty.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/28892/comment/e679b15c_f951f808
PS2, Line 3393: if (!msc->a.bssmap_reset) {
Wording confusion:
- this is not about "Resetting the BSSMAP interface", it is about sending a BSSMAP Reset message to the peer.
- this is not about an unallocated MSC.
If the MSC is not allocated, above 'if (!msc)' triggers.
If bssmap_reset is NULL, then the RESET message handling FSM instance has not been initialized / already torn down.
The code below is about sending a BSSMAP RESET message, so the log should say something like
"Unable to send BSSMAP RESET message, bssmap_reset FSM not allocated"
But did you actually face a situation like this? Seems unlikely to happen.
File src/osmo-bsc/bssmap_reset.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/28892/comment/ef077194_f2e3c53d
PS2, Line 249: LOGP(DMSC, LOGL_ERROR, "Attempt to reset non-existent BSSMAP\n");
No caller should call this function with a NULL argument.
Otherwise we'd need to add such NULL checks to all of the API functions everywhere.
If it is really plausible, then:
Wording confusion: rather "Unable to send BSSMAP RESET message, no FSM instance present"
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/28892
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I235bdd42ea82e7b5a1a40f437ca34c49ad239c48
Gerrit-Change-Number: 28892
Gerrit-PatchSet: 2
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 17 Aug 2022 02:09:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin, msuraev, dexter.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28846 )
Change subject: Make esme struct shared
......................................................................
Patch Set 19: Code-Review-1
(4 comments)
File include/osmocom/smpp/smpp.h:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/75e5796c_038ce042
PS19, Line 14: struct esme {
prefer 'struct smpp_esme' since it is from smpp.h
File include/osmocom/smpp/smpp_smsc.h:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/eb66d78b_c63ea6c8
PS19, Line 32: struct esme *esme;
just 'struct esme esme;' (non-pointer) to avoid extra talloc,
then smpp_esme_init(&osmo_esme.esme) instead of esme_alloc()
File src/libsmpputil/smpp_smsc.c:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/dcef0350_bd4e35a1
PS19, Line 900: esme->esme = esme_alloc(esme);
...because the esme_alloc() appears to unconditionally take place after talloc(struct osmo_esme) anyway.
File src/utils/Makefile.am:
https://gerrit.osmocom.org/c/osmo-msc/+/28846/comment/f65950f5_9b47607a
PS19, Line 45: $(top_builddir)/src/libvlr/libvlr.a \
smpp_mirror certainly does not need libvlr.a.
also looks weird to require libmsc.a.
and pull in ASN1C, SIGTRAN and SQLITE3 below...
can you find a way to not pull in all sorts of unrelated dependencies?
just guessing, maybe move the esme implementation from libmsc to libsmpputil?
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28846
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I8f7ac2c00d16660925dd0b03aa1a0973edf9eb70
Gerrit-Change-Number: 28846
Gerrit-PatchSet: 19
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 17 Aug 2022 01:47:18 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o…
Package network:osmocom:nightly/osmo-iuh failed to build in Raspbian_11/armv7l
Check out the package for editing:
osc checkout network:osmocom:nightly osmo-iuh
Last lines of build log:
[ 196s] update-alternatives: using /usr/share/docutils/scripts/python3/rst2xml to provide /usr/bin/rst2xml (rst2xml) in auto mode
[ 196s] update-alternatives: using /usr/share/docutils/scripts/python3/rstpep2html to provide /usr/bin/rstpep2html (rstpep2html) in auto mode
[ 197s] [452/485] installing python3-reportlab-3.5.59-2
[ 199s] [453/485] installing g++-4:10.2.1-1+rpi1
[ 199s] update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
[ 199s] [454/485] installing libosmo-netif-dev-1.2.0.7.c824.202208170052
[ 200s] [455/485] installing mount-2.36.1-8+deb11u1
[ 200s] [456/485] installing texlive-latex-extra-2020.20210202-3
[ 203s] [457/485] installing debhelper-13.3.4
[ 204s] [458/485] installing bash-5.1-2+deb11u1
[ 205s] update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
[ 205s] [459/485] installing libosmo-sigtran-dev-1.6.0.1.e6ce.202208170052
[ 205s] [460/485] installing build-essential-12.9
[ 205s] [461/485] installing python3-blockdiag-2.0.1+dfsg-1
[ 206s] [462/485] installing texlive-xetex-2020.20210202-3
[ 208s] dpkg-deb (subprocess): decompressing archive '.init_b_cache/texlive-xetex.deb' (size=12542520) member 'data.tar': lzma error: compressed data is corrupt
[ 208s] dpkg-deb: error: <decompress> subprocess returned error exit status 2
[ 208s] dpkg: error processing archive .init_b_cache/texlive-xetex.deb (--install):
[ 208s] cannot copy extracted data for './usr/share/doc/texlive-doc/xetex/xesearch/xesearch.pdf' to '/usr/share/doc/texlive-doc/xetex/xesearch/xesearch.pdf.dpkg-new': unexpected end of file or stream
[ 208s] Errors were encountered while processing:
[ 208s] .init_b_cache/texlive-xetex.deb
[ 208s] exit ...
[ 208s] ### VM INTERACTION START ###
[ 208s] [ 183.908582] sysrq: SysRq : Power Off
[ 208s] [ 183.910438] reboot: Power down
[ 208s] ### VM INTERACTION END ###
[ 208s]
[ 208s] armbuild02 failed "build osmo-iuh_1.3.0.2.a9c38.202208170052.dsc" at Wed Aug 17 01:36:59 UTC 2022.
[ 208s]
--
Configure notifications at https://build.opensuse.org/my/subscriptions
openSUSE Build Service (https://build.opensuse.org/)
Attention is currently required from: msuraev.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-sccp/+/29085 )
Change subject: Log more data on CR and N-CONNECT
......................................................................
Patch Set 7: Code-Review+1
(1 comment)
Patchset:
PS7:
i'd solve this question by looking at wireshark instead of logging?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sccp/+/29085
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-sccp
Gerrit-Branch: master
Gerrit-Change-Id: I4d7fc44fde5b900907ec5ebec0450040a764802a
Gerrit-Change-Number: 29085
Gerrit-PatchSet: 7
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 17 Aug 2022 01:15:14 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment