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/+/38375?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: ss7 vty: Fix insert order of routes with higher priority ......................................................................

ss7 vty: Fix insert order of routes with higher priority

Route lookup ((hmrt_message_for_routing() => osmo_ss7_route_lookup() => osmo_ss7_route_find_dpc_mask())) iterates the list of routes assuming they are ordered by mask length (so it doesn't need to iterate the full list every time). Similary, it implicitly seems to assume that the entries are also sorted by priority.

However, priority is not currently taken into account when being inserted in the routing table, so the route ends up in the incorrect place.

The VTY "update route" command used to first insert the route and only *after* that tweak some of its fields, like priority or qos-class.

This commit adds a new set of osmo_ss7_route API which allows users to *first* allocate a route and configure it completelly, and *second* insert it once it contains all the information. This way, the insert algorithm can take into account the configured route priority and place the route entry in the routing table at the proper place.

Related: SYS#7112 Change-Id: I6e7b5e3f06ae2c9468da58c55d2f42cbcd777218 --- M TODO-RELEASE M include/osmocom/sigtran/osmo_ss7.h M src/osmo_ss7.c M src/osmo_ss7_vty.c M tests/vty/osmo_stp_route_prio.vty 5 files changed, 200 insertions(+), 55 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/libosmo-sigtran refs/changes/75/38375/2