fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37802?usp=email )
Change subject: erab_fsm: fix API docs: UID was moved to start_link()
......................................................................
erab_fsm: fix API docs: UID was moved to start_link()
Change-Id: I4987baac8f2da30a6d285275eaba2cac0528ac93
---
M src/erab_fsm.erl
1 file changed, 4 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/erlang/osmo-s1gw refs/changes/02/37802/1
diff --git a/src/erab_fsm.erl b/src/erab_fsm.erl
index 5635086..8a9d0ec 100644
--- a/src/erab_fsm.erl
+++ b/src/erab_fsm.erl
@@ -80,6 +80,10 @@
%% public API
%% ------------------------------------------------------------------
+%% @doc Allocate and start an E-RAB FSM process
+%% @param UID *unique* E-RAB identifier.
+%% @returns process ID on success; an error otherwise.
+%% @end
-spec start_link(term()) -> gen_statem:start_ret().
start_link(UID) ->
gen_statem:start_link(?MODULE, [UID], []).
@@ -87,7 +91,6 @@
%% @doc Indicate reception of E-RAB setup request (from the eNB).
%% @param Pid PID of an erab_fsm.
-%% @param UID *unique* E-RAB identifier.
%% @param TEID TEID chosen by the eNB.
%% @returns TEID to be sent to the core; an error otherwise.
%% @end
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37802?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: I4987baac8f2da30a6d285275eaba2cac0528ac93
Gerrit-Change-Number: 37802
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: fixeria, jolly.
laforge has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email )
Change subject: After writing VTY config, run sync() in a different thread
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> Not saying there can't be a better way, though ;) […]
I am quite sure the reason is "because it was easy to do". We don't care about whatever operations happen on the old file. We really only care that the newly written file has been written. So IMHO what is needed is fsync() on the [new] file itself, as well as fsync to the directory cotnaining the file. The "link" call (working with path names) might need to change to "linkat" (work with directory file descriptors)?
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
Gerrit-Change-Number: 37798
Gerrit-PatchSet: 2
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 12 Aug 2024 19:04:47 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: jolly, laforge.
fixeria has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email )
Change subject: After writing VTY config, run sync() in a different thread
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> We had this discussion with @andreas@eversberg. […]
Not saying there can't be a better way, though ;)
It's just my understanding. Letting @andreas@eversberg.eu to comment here.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
Gerrit-Change-Number: 37798
Gerrit-PatchSet: 2
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 12 Aug 2024 17:55:13 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: jolly, laforge.
fixeria has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email )
Change subject: After writing VTY config, run sync() in a different thread
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> while this is an improvement, we ideally would only call fsync on the one specific file, rather than […]
We had this discussion with @andreas@eversberg.eu in a call, and at first I was also under impression that this is complicating things and we should just go for `fsync()`. But then we checked the code and I found out that it's not just writing stuff to one file, but doing several fs operations: `mkstemp()`, write to it, `unlink()`, `stat()`, than `link()` and `unlink()`. This made me think that the code is doing `sync()` for a reason.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/37798?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3cb2ee68b2e4c730f96522208c4abf00d0f49a44
Gerrit-Change-Number: 37798
Gerrit-PatchSet: 2
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 12 Aug 2024 17:53:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Attention is currently required from: fixeria.
laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/pysim/+/37690?usp=email )
Change subject: recognize ADF.PKCS15, allow selecting it
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
File pySim/pkcs15.py:
https://gerrit.osmocom.org/c/pysim/+/37690/comment/dca71239_960bb2ce?usp=em… :
PS1, Line 32: files = [
might be worth adding a TODO / FIXME comment about this needing code to discover the files at runtime. I think we already have similar comments in other locations where this hapepns, like EF.ICON in DF.GRAPHICS or other instances?
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/37690?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I7ea6d91805868645ae1c1a4a2c5870f7d041f74b
Gerrit-Change-Number: 37690
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 12 Aug 2024 17:46:02 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes