neels has uploaded a new patch set (#2). ( https://gerrit.osmocom.org/c/libosmocore/+/32576 )
Change subject: vty: move struct vty_parent_node to private API
......................................................................
vty: move struct vty_parent_node to private API
Change-Id: Id2070f03b09feea966c5342361d409551e557d38
---
M TODO-RELEASE
M include/osmocom/vty/vty.h
M src/vty/command.c
3 files changed, 26 insertions(+), 16 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/76/32576/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32576
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Id2070f03b09feea966c5342361d409551e557d38
Gerrit-Change-Number: 32576
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-CC: Jenkins Builder
Gerrit-MessageType: newpatchset
Attention is currently required from: laforge, pespin, fixeria.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmocore/+/32561
to look at the new patch set (#2).
Change subject: vty: show bug in implicit go_parent_node
......................................................................
vty: show bug in implicit go_parent_node
Add test to show a problem in VTY node exiting.
Back in 2017 when I introduced VTY config file scopes by indenting [1],
I actually mistook the vty->priv for the vty->index that we use
everywhere to link to the state for our VTY nodes.
The intention was that each VTY node child level has its own object
linked to it by the vty->index pointer. When the config file leaves a
scope, the vty->index should reflect the parent object.
Instead I implemented that for the vty->priv pointer only, but we don't
use that.
Why did this bug not show? A problem happens only if:
- a node that uses vty->index is nested inside a node that also uses
vty->index.
- config sets parent node attributes after a child node.
- there is no legacy vty_go_parent() function that sets the correct
index via a switch().
[1]
"VTY: implicit node exit by de-indenting, not parent lookup"
4a31ffa2f0097d96201f80305a0495c57552f0ad
I24cbb3f6de111f2d31110c3c484c066f1153aac9
Change-Id: I2472daed7436a1947655b06d34eb217e595bc7f3
---
M tests/vty/vty_transcript_test.c
M tests/vty/vty_transcript_test.vty
2 files changed, 138 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/61/32561/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32561
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I2472daed7436a1947655b06d34eb217e595bc7f3
Gerrit-Change-Number: 32561
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: 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
Attention is currently required from: pespin, fixeria.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/32562 )
Change subject: vty: fix vty->index for implicit go_parent_node
......................................................................
Patch Set 1:
(1 comment)
File include/osmocom/vty/vty.h:
https://gerrit.osmocom.org/c/libosmocore/+/32562/comment/6cbb48b6_806d20af
PS1, Line 64: void *index;
> Ack
no caller ever accesses struct vty_parent_node, it is used internally to remember the VTY scopes being entered and exited; looking back at it now, this should never have become public API, but we were so young and naive...
So I assure you that it is safe to put the new member in a human readable place.
Could be an idea to move this struct def to the static vty/command.c scope
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32562
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Id408c678d18ba19b1c1394c3fb657536153d2094
Gerrit-Change-Number: 32562
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(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: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 03 May 2023 00:27:11 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: laforge, pespin, fixeria.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/32561 )
Change subject: vty: show bug in implicit go_parent_node
......................................................................
Patch Set 1:
(2 comments)
Commit Message:
https://gerrit.osmocom.org/c/libosmocore/+/32561/comment/21d2eaba_a3e84e25
PS1, Line 26: there is no legacy vty_go_parent() function that sets the correct
: index via a switch().
> note: Some of them cannot be dropped since they are used as hooks to do stuff like applying the new […]
yes, for example in cs7 config, the go_parent_cb() does the action of applying config changes.
But we can definitely get rid of all the *unnecessary* go_parent_cb()s, and all go_parent code that merely sets vty->node to a new constant. I've been doing that here and there over the years already...
File tests/vty/vty_transcript_test.c:
https://gerrit.osmocom.org/c/libosmocore/+/32561/comment/53aa5949_5f132bfd
PS1, Line 344: talloc_asprintf(root_ctx, argv[0]);
> `-Werror=format-security`: should be `...(root_ctx, "%s", argv[0]);`. […]
yes, seems i wasn't paying attention, thx
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32561
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I2472daed7436a1947655b06d34eb217e595bc7f3
Gerrit-Change-Number: 32561
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: 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: Wed, 03 May 2023 00:22:28 +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: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: comment
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmo-gprs/+/32574
to look at the new patch set (#2).
Change subject: gmm: Fix typo in param name passed to logging macro
......................................................................
gmm: Fix typo in param name passed to logging macro
Change-Id: Ib8025f29ddd9916907e14becaadad66336306e8a
---
M include/osmocom/gprs/gmm/gmm_private.h
1 file changed, 10 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-gprs refs/changes/74/32574/2
--
To view, visit https://gerrit.osmocom.org/c/libosmo-gprs/+/32574
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-gprs
Gerrit-Branch: master
Gerrit-Change-Id: Ib8025f29ddd9916907e14becaadad66336306e8a
Gerrit-Change-Number: 32574
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-MessageType: newpatchset
Attention is currently required from: laforge, fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/32560 )
Change subject: oml: reset BCCH carrier power reduction mode (if enabled)
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
Patchset:
PS2:
Did you actually test the patch to make sure it does what you want in there?
I pointed to that place because it's where all bts state fields should be reset, but perhaps you want to do soemthing different here.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/32560
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I34468e3fccc490f48e30b159b63308a395b65fa9
Gerrit-Change-Number: 32560
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 02 May 2023 19:15:29 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment