Started by an SCM changeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.org00001167131167131.05958595801226715956595610846da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/masterhttps://gerrit.osmocom.org/libosmo-sigtranhttps://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/1084/artifacthttps://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/changeshttps://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/1084/https://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/1084/testReportfalse#108411671373813master-libosmo-sigtran #10841084falsefalse108476839SUCCESS1774965066403https://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/1084/src/m3ua.c91625d666c2dfe109c64868e5aecf12e71f90d2d1774964289000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: 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 identified. 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 2026-03-31 15:38:09 +020091625d666c2dfe109c64868e5aecf12e71f90d2dm3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.csrc/xua_asp_fsm.c1d41fef4999a4c0b8050e4ee01ccf0914c1912ca1774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routing Context As per RFC4666 3.8.1: """ For this error, the invalid Routing Context(s) MUST be included in the Error message. """ Change-Id: Ia8bff16248967209d73cd6d5b54ac30fda283247 2026-03-31 15:38:19 +02001d41fef4999a4c0b8050e4ee01ccf0914c1912caxua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routingeditsrc/xua_asp_fsm.csrc/xua_as_fsm.c6da14bb48f02f15d476b72e0d2113194e5979c011774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDING Queueing of messags during T(r) (state PENDING) is already implemented, see xua_as_fsm_pending() further below in the same file. Change-Id: Ie572367493066039f7022250d94b815a4da5bd16 2026-03-31 15:38:19 +02006da14bb48f02f15d476b72e0d2113194e5979c01xua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDINGeditsrc/xua_as_fsm.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin PedrolpespinBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.orgStarted by upstream project "master-libosmo-sigtran" build number 1,0841084master-libosmo-sigtranjob/master-libosmo-sigtran/000078100781001.000010846da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/masterhttps://gerrit.osmocom.org/libosmo-sigtranfalse#10847810044789master-libosmo-sigtran » WITH_MANUALS=0,WITH_TCAP=0,a3=default,a4=default,osmocom-master #10841084falsefalse108476841SUCCESS1774965066403https://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/WITH_MANUALS=0,WITH_TCAP=0,a3=default,a4=default,label=osmocom-master/1084/build5-deb12build-ansiblesrc/m3ua.c91625d666c2dfe109c64868e5aecf12e71f90d2d1774964289000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: 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 identified. 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 2026-03-31 15:38:09 +020091625d666c2dfe109c64868e5aecf12e71f90d2dm3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.csrc/xua_asp_fsm.c1d41fef4999a4c0b8050e4ee01ccf0914c1912ca1774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routing Context As per RFC4666 3.8.1: """ For this error, the invalid Routing Context(s) MUST be included in the Error message. """ Change-Id: Ia8bff16248967209d73cd6d5b54ac30fda283247 2026-03-31 15:38:19 +02001d41fef4999a4c0b8050e4ee01ccf0914c1912caxua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routingeditsrc/xua_asp_fsm.csrc/xua_as_fsm.c6da14bb48f02f15d476b72e0d2113194e5979c011774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDING Queueing of messags during T(r) (state PENDING) is already implemented, see xua_as_fsm_pending() further below in the same file. Change-Id: Ie572367493066039f7022250d94b815a4da5bd16 2026-03-31 15:38:19 +02006da14bb48f02f15d476b72e0d2113194e5979c01xua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDINGeditsrc/xua_as_fsm.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin PedrolBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.orgStarted by upstream project "master-libosmo-sigtran" build number 1,0841084master-libosmo-sigtranjob/master-libosmo-sigtran/00001153831153831.000010846da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/master6da14bb48f02f15d476b72e0d2113194e5979c016da14bb48f02f15d476b72e0d2113194e5979c01origin/masterhttps://gerrit.osmocom.org/libosmo-sigtranfalse#108411538370543master-libosmo-sigtran » WITH_MANUALS=1,WITH_TCAP=1,a3=default,a4=default,osmocom-master #10841084falsefalse108476840SUCCESS1774965066403https://jenkins.osmocom.org/jenkins/view/registry/job/master-libosmo-sigtran/WITH_MANUALS=1,WITH_TCAP=1,a3=default,a4=default,label=osmocom-master/1084/build5-deb12build-ansiblesrc/m3ua.c91625d666c2dfe109c64868e5aecf12e71f90d2d1774964289000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: 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 identified. 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 2026-03-31 15:38:09 +020091625d666c2dfe109c64868e5aecf12e71f90d2dm3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.csrc/xua_asp_fsm.c1d41fef4999a4c0b8050e4ee01ccf0914c1912ca1774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routing Context As per RFC4666 3.8.1: """ For this error, the invalid Routing Context(s) MUST be included in the Error message. """ Change-Id: Ia8bff16248967209d73cd6d5b54ac30fda283247 2026-03-31 15:38:19 +02001d41fef4999a4c0b8050e4ee01ccf0914c1912caxua_asp_fsm: Include Routing Context IE in Err msg cuase Invalid Routingeditsrc/xua_asp_fsm.csrc/xua_as_fsm.c6da14bb48f02f15d476b72e0d2113194e5979c011774964299000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dexua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDING Queueing of messags during T(r) (state PENDING) is already implemented, see xua_as_fsm_pending() further below in the same file. Change-Id: Ie572367493066039f7022250d94b815a4da5bd16 2026-03-31 15:38:19 +02006da14bb48f02f15d476b72e0d2113194e5979c01xua_as_fsm: Remove FIXME regarding queueing of msgs during state PENDINGeditsrc/xua_as_fsm.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol