neels has submitted this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/32038 )

Change subject: release UE Contexts on SCTP_RESTART ......................................................................

release UE Contexts on SCTP_RESTART

When receiving SCTP_RESTART for a given HNB, directly clear the UE Contexts.

(The HNB typically connects via HNBAP shortly after this causing a UE Context clearing too, but UE state should always be cleared on SCTP_RESTART, no matter what.)

Change-Id: I583922193ba73e17ab85152005535188c2762b85 --- M src/osmo-hnbgw/hnbgw.c 1 file changed, 17 insertions(+), 0 deletions(-)

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved

diff --git a/src/osmo-hnbgw/hnbgw.c b/src/osmo-hnbgw/hnbgw.c index 5b4e9b6..0624803 100644 --- a/src/osmo-hnbgw/hnbgw.c +++ b/src/osmo-hnbgw/hnbgw.c @@ -264,6 +264,7 @@ case SCTP_RESTART: LOGHNB(hnb, DMAIN, LOGL_NOTICE, "HNB SCTP conn RESTARTed, marking as HNBAP-unregistered\n"); hnb->hnb_registered = false; + hnb_context_release_ue_state(hnb); /* The tx queue may be quite full after an SCTP RESTART: (SYS#6113) * The link may have been flaky (a possible reason for the peer restarting the conn) and * hence the kernel socket Tx queue may be full (no ACKs coming back) and our own userspace