Attention is currently required from: pespin.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmo-sigtran/+/42536?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified-1 by Jenkins Builder
Change subject: m3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context
......................................................................
m3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context
As per RFC4666 3.8.1:
"""
The "Invalid Routing Context" error is sent if a message is received
from a peer with an invalid (unconfigured) Routing Context value.
For this error, the invalid Routing Context(s) MUST be included in
the Error message."
"""
Hence add the originating Routing Context IE so the error message can be
further originated.
For the same reason, also add the Diagnostic Information for the
specific cases in the switch statement, and make them more robust about
possible null pointer dereference.
Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd
---
M src/m3ua.c
1 file changed, 16 insertions(+), 8 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-sigtran refs/changes/36/42536/2
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/42536?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd
Gerrit-Change-Number: 42536
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/42536?usp=email )
Change subject: m3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context
......................................................................
m3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context
As per RFC4666 3.8.1:
"""
The "Invalid Routing Context" error is sent if a message is received
from a peer with an invalid (unconfigured) Routing Context value.
For this error, the invalid Routing Context(s) MUST be included in
the Error message."
"""
Hence add the originating Routing Context IE so the error message can be
further originated.
For the same reason, also add the Diagnostic Information for the
specific cases in the switch statement, and make them more robust about
possible null pointer dereference.
Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd
---
M src/m3ua.c
1 file changed, 15 insertions(+), 8 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-sigtran refs/changes/36/42536/1
diff --git a/src/m3ua.c b/src/m3ua.c
index 3980bd3..368d4c3 100644
--- a/src/m3ua.c
+++ b/src/m3ua.c
@@ -383,7 +383,6 @@
{
struct xua_msg *err = m3ua_gen_error(err_code);
struct xua_msg *xua;
- struct xua_msg_part *na_ie;
unsigned int len_max_40;
if (!err)
@@ -393,18 +392,26 @@
case M3UA_ERR_INVAL_NET_APPEAR:
/* Include NA IE in Error message. */
xua = xua_from_msg(M3UA_VERSION, msgb_length(msg), msgb_data(msg));
- na_ie = xua_msg_find_tag(xua, M3UA_IEI_NET_APPEAR);
- xua_msg_add_data(err, M3UA_IEI_NET_APPEAR, na_ie->len, na_ie->dat);
+ if (xua)
+ xua_msg_copy_part(err, M3UA_IEI_NET_APPEAR, xua, M3UA_IEI_NET_APPEAR);
+ xua_msg_free(xua);
+ break;
+ case M3UA_ERR_INVAL_ROUT_CTX:
+ /* Include Routing Context IE if available: */
+ xua = xua_from_msg(M3UA_VERSION, msgb_length(msg), msgb_data(msg));
+ if (xua)
+ xua_msg_copy_part(err, M3UA_IEI_ROUTE_CTX, xua, M3UA_IEI_ROUTE_CTX);
xua_msg_free(xua);
break;
default:
- len_max_40 = msgb_length(msg);
- if (len_max_40 > 40)
- len_max_40 = 40;
-
- xua_msg_add_data(err, M3UA_IEI_DIAG_INFO, len_max_40, msgb_data(msg));
}
+ len_max_40 = msgb_length(msg);
+ if (len_max_40 > 40)
+ len_max_40 = 40;
+
+ xua_msg_add_data(err, M3UA_IEI_DIAG_INFO, len_max_40, msgb_data(msg));
+
return err;
}
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/42536?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd
Gerrit-Change-Number: 42536
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ci/+/42535?usp=email
to look at the new patch set (#2).
Change subject: OBS: nightly: add ".0" after versions on git tags
......................................................................
OBS: nightly: add ".0" after versions on git tags
Fix that with the current logic of generating version numbers for
nightly, a version done on a tag can be higher than the following
version:
on tag: 1.14.0.202603231800
on tag (with this patch): 1.14.0.0.202603231800
next commit after the tag: 1.14.0.1.abcd.202603241800
Fixes: OS#6981
Change-Id: Id140d8ea76bf98357711587a9909d54097250fd6
---
M scripts/obs/lib/srcpkg.py
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/35/42535/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/42535?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: Id140d8ea76bf98357711587a9909d54097250fd6
Gerrit-Change-Number: 42535
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ci/+/42535?usp=email )
Change subject: OBS: nightly: add ".0" after versions on git tags
......................................................................
OBS: nightly: add ".0" after versions on git tags
Fix that with the current logic of generating version numbers for
nightly, a version done on a tag can be higher than the following
version:
on tag: 1.14.0.202603231800 # <tag>.<YY><MM><DD><HH><mm><SS>
on tag (with this patch): 1.14.0.0.202603231800 # <tag>.0.<YY><MM><DD><HH><mm><SS>
next commit after the tag: 1.14.0.1.2016.202603241800 # <tag>.<patch-count-since-last-tag>.<commit-hash>.<YY><MM><DD><HH><mm><SS>
Fixes: OS#6981
Change-Id: Id140d8ea76bf98357711587a9909d54097250fd6
---
M scripts/obs/lib/srcpkg.py
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/35/42535/1
diff --git a/scripts/obs/lib/srcpkg.py b/scripts/obs/lib/srcpkg.py
index b3e0422..8ed50df 100644
--- a/scripts/obs/lib/srcpkg.py
+++ b/scripts/obs/lib/srcpkg.py
@@ -106,6 +106,12 @@
if ":" in ret:
ret = ret.split(":")[1]
+ # Nightly: add a ".0" after the version if the current commit is on a
+ # version tag, so the next version is higher (OS#6981)
+ if lib.args.feed == "nightly":
+ while ret.count(".") < 3:
+ ret += ".0"
+
# Append the conflict_version to increase the version even if the commit
# did not change (OS#5135)
conflict_version = lib.args.conflict_version
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/42535?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: Id140d8ea76bf98357711587a9909d54097250fd6
Gerrit-Change-Number: 42535
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>