Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/32626 )
Change subject: drop ctrl_test_runner.py
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> or we could add a test :D
yea true ... but this foo_test_runner.py stuff is from before we had VTY and CTRL transcript testing. The transcript testing is much much quicker and easier to write, plus mostly runs much faster. So i reallly doubt that anyone is going to add tests to the ctrl_test_runner.py when we have foo.ctrl transcript testing. Or actually it's my personal agenda that i don't want anyone to ever write ctrl_test_runner tests anymore.
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/32626
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: If3d6614334b692e49efcc45d1e4fb29a00c68602
Gerrit-Change-Number: 32626
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 May 2023 19:39:53 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/32627 )
Change subject: vty: fix doc strings for 'show {hnb,ue}'
......................................................................
Patch Set 2:
(1 comment)
File src/osmo-hnbgw/hnbgw_vty.c:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/32627/comment/4e4afa58_ea8a88a8
PS2, Line 269: SHOW_STR "Display HNBAP information about UE\n" "All UE\n")
> are you sure this is only HNBAP information?
yep. maybe this can be more elaborate in the future, but ue_context is only HNBAP and actually completely unused by osmo-hnbgw
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/32627
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I79f8b13a9f22fb8311017005cc0a3ac3a7e78983
Gerrit-Change-Number: 32627
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 May 2023 19:37:25 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: pespin, dexter.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32606 )
Change subject: PCUIF_Types: add record PCUIF_pch_dt
......................................................................
Patch Set 2: Code-Review-1
(2 comments)
File library/PCUIF_Types.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32606/comment/c93d7381_98d1…
PS1, Line 320: octetstring data length(162)
> But a mac block is 23 bytes -> 184 bits?
162 is not bits here, it's actually bytes. One MAC block in GSM (since we're talking about PCH) is 23 bytes long, so it should be `data length(23)`. I just checked `pcuif_proto.h`, and I see `uint8_t data[GSM_MACBLOCK_LEN]` in `struct gsm_pcu_if_pch_dt`.
File library/PCUIF_Types.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32606/comment/a28e163f_f666…
PS2, Line 319: octetstring
Can we use `charstring` here? It would have been more convenient.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32606
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: Ia705d3a6fe7adb863acd29e968f8dc6b2066a497
Gerrit-Change-Number: 32606
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 May 2023 18:01:51 +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
Attention is currently required from: osmith, laforge, fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/32641 )
Change subject: fix use-after-free in ipaccess_bts_keepalive_fsm_alloc()
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
Summary of what this patch does as I finally understood it:
> ah ok, you are advancing osmo_fsm_inst_free() by advancing call to ipaccess_keepalive_fsm_cleanup()
> and then that means when the other struct is freed, the fsm is already properly freed beforehand, so it doesn't free it implicitly with talloc_free()"
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/32641
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: Ic56c4b5b7b24b63104908a0c24f2f645ba4c5c1b
Gerrit-Change-Number: 32641
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(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-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 May 2023 17:47:33 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/32641 )
Change subject: fix use-after-free in ipaccess_bts_keepalive_fsm_alloc()
......................................................................
Patch Set 1:
(2 comments)
Commit Message:
https://gerrit.osmocom.org/c/libosmo-abis/+/32641/comment/8127499a_dfc877f6
PS1, Line 31: *** (!) as well as the struct osmo_fsm_inst (talloc child)
> shouldn't the fsm always be freed with explicit osmo_fsm_inst_free() and not through automatic tallo […]
Yes, all `osmo_fsm_inst` should normally be freed by calling `osmo_fsm_inst_free()`. But in this specific case it gets free()d implicitly (and incorrectly, not cleaning up stuff like timers and llists) before we reach the point of calling `osmo_fsm_inst_free()`. And when we call it, osmo-bts crashes due to use-after-free.
https://gerrit.osmocom.org/c/libosmo-abis/+/32641/comment/67473659_0c543803
PS1, Line 33: *** calling ipaccess_keepalive_fsm_cleanup()
> why is cleanup() called here if it was freed above?
I don't know why the cleanup() is called in the alloc() function... ask Eric.
> why wasn't the pointer set to NULL?
talloc does not set pointers to NULL when free()ing child chunks...
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/32641
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: Ic56c4b5b7b24b63104908a0c24f2f645ba4c5c1b
Gerrit-Change-Number: 32641
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 May 2023 17:44:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment