From 9f16a869a514500b9ede709334d67a173d59b174 Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Sat, 22 Aug 2009 11:18:13 +0200 Subject: [subscr] subscr_paging_cb is called for expire and success Gracefully handle a case where success and expire could fire... I'm only hitting this when doing something evil to simulate network code but it seems appropriate to handle this gracefully. --- openbsc/src/gsm_subscriber_base.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'openbsc/src/gsm_subscriber_base.c') diff --git a/openbsc/src/gsm_subscriber_base.c b/openbsc/src/gsm_subscriber_base.c index 54db44774..868b35599 100644 --- a/openbsc/src/gsm_subscriber_base.c +++ b/openbsc/src/gsm_subscriber_base.c @@ -73,7 +73,9 @@ static int subscr_paging_cb(unsigned int hooknum, unsigned int event, struct subscr_request *request; struct gsm_subscriber *subscr = (struct gsm_subscriber *)param; - assert(!llist_empty(&subscr->requests)); + /* There is no request anymore... */ + if (llist_empty(&subscr->requests)) + return -1; /* * FIXME: What to do with paging requests coming during -- cgit v1.2.3