mirror of
https://gerrit.osmocom.org/osmo-gbproxy
synced 2024-08-18 08:56:23 +00:00
[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.
This commit is contained in:
parent
aca08d90d3
commit
aa62bb985a
1 changed files with 3 additions and 1 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue