This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, jerlbeck/wip/gprs-patching has been updated
discards fc376259e0a306d41e17cab43de7c2a4796f9aba (commit)
discards bf5805ff4d5e0433185811a359baccc2e73f32ce (commit)
discards f567963a36a541a46bd226632c7368c3d507c064 (commit)
discards 147cf8a851eedf117450541ba068ced3f802f1dc (commit)
discards d06b20c0a9e171ba9143d73e882c44c3b9b0744d (commit)
discards 93a0fcd78a9e2d0c7fdf9ad90be3f41619ce5c2e (commit)
discards c7c48fa68cd9e4790c9883b0f6031bd73a2dd737 (commit)
discards 8dec82b096df85227171eea0d34cf6cfbea3724e (commit)
discards 50a0d6984536691466b6154288ddc83f1defae9c (commit)
discards 249a5375c66e1d3560218eeedbc7a1c524673275 (commit)
discards bd4d5bb2c921e7e6333019fda885430ebd3aa3df (commit)
discards a5b9ea754883d2d7a547ba4b2da7c3fb8c40efc0 (commit)
discards f47dc130732e3a29fc729d9f859231646c5cac6c (commit)
via 89b5af1f8d450e039602030d06ea6b0bd62925a2 (commit)
via 488cc66679e20973fc85c4bc9a39eacf46548f80 (commit)
via 51d8be51f7a4c099a72a5ebc025f3daf8710918d (commit)
via cfe222efff4a215043b6828d246b433e2faa0710 (commit)
via 71e61686c3a469f057636eec6ff2003affdbe1c1 (commit)
via c20303e00196a96b08d5be4e716774983ea92fce (commit)
via 328c5c1d40aecfe2c72e352d0d6beda4b7c86f86 (commit)
via 5355202011c9ac4a751608ecdb7d825c7f335d1e (commit)
via 7ed031b2c876d8c2ab1471d27569131c683011ee (commit)
via 77057d0820690d6f67716670ff94b240b370c118 (commit)
via 157392a168916b6828676d53d943b099e0d0708d (commit)
via 0df73b1093c7d720cc64fa967a2268a13a929c72 (commit)
via aee0cdc4db6d34855597ebe7e09abc647d8e692e (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (fc376259e0a306d41e17cab43de7c2a4796f9aba)
\
N -- N -- N (89b5af1f8d450e039602030d06ea6b0bd62925a2)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=89b5af1f8d450e039602030d06ea6b0b…
commit 89b5af1f8d450e039602030d06ea6b0bd62925a2
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Sep 30 13:53:26 2014 +0200
sgsn: Added TODOs (TODO)
TODO:
- fix and remove TODOs
- add test cases for Detach(reattach)
- add test cases for PDP context deletion (OW#1311)
- add test cases for Cancel pending timer in sgsn_mm_ctx_free
- implement age based MM context expiry
- remove this commit
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=488cc66679e20973fc85c4bc9a39eacf…
commit 488cc66679e20973fc85c4bc9a39eacf46548f80
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Oct 17 10:08:02 2014 +0200
sgsn: Do not die in _bssgp_tx_dl_ud on TLLI mismatch (TODO)
Currently an OSMO_ASSERT fails, if the message's and the mmctx's
TLLIs do not match.
This commit turns the assertion into an ERROR log message and uses
the default values for IMSI, DRX, and RA CAP instead of the MM
context values in this case.
TODO:
- find the real source for the problem
- add test cases derived from what is being described in the ticket
Ticket: OW#1322
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=51d8be51f7a4c099a72a5ebc025f3daf…
commit 51d8be51f7a4c099a72a5ebc025f3daf8710918d
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed Dec 17 14:03:35 2014 +0100
sgsn: Add PDP info to subscriber data (TODO)
TODO:
- commit message
- raw binary representation ???
- tests
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=cfe222efff4a215043b6828d246b433e…
commit cfe222efff4a215043b6828d246b433e2faa0710
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Dec 19 19:11:20 2014 +0100
sgsn: Add logging to connect_timer_cb (TODO)
TODO:
- LOGLevel ?
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=71e61686c3a469f057636eec6ff2003a…
commit 71e61686c3a469f057636eec6ff2003affdbe1c1
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Jan 13 11:56:28 2015 +0100
gprs: Fix GSUP msgb freeing
Currently the code relies on the lower layers (socket read) to free
the msgb after the callbacks have been processed linke it is being
done in the NS layer. Unfortunately the IPA client connection
implementation does this differently so the current msgb handling in
the GSUP related code in broken at the moment and leaks msgbs.
This patch adds missing calls to msgb_free.
The talloc report in sgsn_test no longer contains msgbs.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=c20303e00196a96b08d5be4e71677498…
commit c20303e00196a96b08d5be4e716774983ea92fce
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Jan 13 11:46:32 2015 +0100
sgsn/test: Add checks and reports to detect leakage
This commit adds talloc reports to log remaining chunks after the
testing has been finished. It also adds explicit checks for an empty
subscriber list.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=328c5c1d40aecfe2c72e352d0d6beda4…
commit 328c5c1d40aecfe2c72e352d0d6beda4b7c86f86
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Jan 9 09:46:43 2015 +0100
sgsn/doc: Add message definitions for PURGE_MS responses
Currently the definitions of the message PURGE_MS_RES and
PURGE_MS_ERR are missing in the specification.
This patch adds those definitions.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=5355202011c9ac4a751608ecdb7d825c…
commit 5355202011c9ac4a751608ecdb7d825c7f335d1e
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Thu Jan 8 15:29:01 2015 +0100
gprs: Support the full cancellation procedure (TODO)
TODO:
- Commit message
- Reply to cancellation request (either with RES or ERR)
Ticket: OW#1338
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=7ed031b2c876d8c2ab1471d27569131c…
commit 7ed031b2c876d8c2ab1471d27569131c683011ee
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Thu Jan 8 16:23:25 2015 +0100
gprs: Block other GSUP procedures during PURGE_MS (TODO)
TODO:
- commit message
- move LOGGSUBSCRP fix in gprs_subscr_purge to HEAD^^
- testing
Ticket: OW#????
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=77057d0820690d6f67716670ff94b240…
commit 77057d0820690d6f67716670ff94b240b370c118
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Thu Jan 8 15:18:39 2015 +0100
gprs: Retry PURGE_MS procedure after timeout
Currently, when the PURGE_MS_REQ to the HLR gets lost (e.g. by a
connection or peer failure), the expired subscriber entry will not get
deleted.
This commit adds a retry mechanism then restarts the procedure after
a timeout (currently 10s). The maximum number of retries is limited
(currently to 3 PURGE_MS messages). If none of these procedures is
completed (either with success or error), the subscriber data is
deleted.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=157392a168916b6828676d53d943b099…
commit 157392a168916b6828676d53d943b099e0d0708d
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Jan 6 16:32:41 2015 +0100
gprs: Support PURGE MS messages
When a subscriber entry is going to be deleted by SGSN and when the
subscriber info has been optained from a remote peer via GSUP, the
peer should be informed before the entry is really deleted. For this
purpose, MAP defines the PURGE MS procedure (see GSM 09.02, 19.1.4).
This patch adds support for the PURGE_MS_REQ/_ERR/_RES messages and
invokes the procedure when the subscriber entry is going to be
removed. This only applies if GSUP is being used, the Update
Location procedure has been completed successfully, and the
subscriber has not been cancelled. The removal of the entry is
delayed until a PURGE_MS_RES or PURGE_MS_ERR message is received.
Ticket: OW#1338
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=0df73b1093c7d720cc64fa967a2268a1…
commit 0df73b1093c7d720cc64fa967a2268a13a929c72
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Jan 9 15:07:16 2015 +0100
sgsn/test: Add test that intercepts gprs_gsup_client_send
This test replaces gprs_gsup_client_send by a custom function, that
emulates a GSUP remote peer by calling gprs_subscr_rx_gsup_message
with responses for all requests. It then executes a full
Attach/Detach cycle.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=aee0cdc4db6d34855597ebe7e09abc64…
commit aee0cdc4db6d34855597ebe7e09abc647d8e692e
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Jan 6 16:32:41 2015 +0100
gprs: Add expiry timeout for subscriber entries
Set the expiry delay after the subscriber has been deleted (e.g. by
freeing the MM context). If cancelled, the subscriber will be deleted
immediately and no timeout will be set. If the expiry time is set to
SGSN_TIMEOUT_NEVER, no timer will be started and the subscriber entry
will be kept until it is cancelled.
The following VTY command is added to the sgsn node:
- subscriber-expiry-time <0-999999> set expiry time in seconds
- no subscriber-expiry-time set to SGSN_TIMEOUT_NEVER
The default is an expiry time of 0 seconds, which means that the
subscriber entries are wiped out immediately after an MM context is
destroyed.
Note that unused MM contexts are not expired yet. Therefore the
subscriber will only be expired after a successful MM detach.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)