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 c11f61401664eb9bb8282445356f5ca851ac1265 (commit) discards f2a3d66e09ba7b0f986dcc54796a0228402ecbca (commit) discards 469b80457e4627c5fd9cbcadedfe27cd9f569b4c (commit) discards 44408848c85a85b0437bb810f8589f696a099fe5 (commit) discards cf1c80f0db0b431d7cc2afe2bda4ee43d596df11 (commit) discards 200b4689c90841ac18cc0754c7a3a95d3c4e4de4 (commit) discards d272b4c7c8c9e2d8a510c85896a661c312d96c0a (commit) discards 09695de8c253ab5ee271c372ea21fd84f7377b99 (commit) discards fa11430d857f006459664e7314a6be79e21a20dd (commit) via 1789a16e884fa069bc2244791a4659c84efdffc8 (commit) via 08001dc2d5c02f67622de15fe7b36bc6b7098bda (commit) via 83c92aca6904b44f129c3aa2dbced8cc0bacea91 (commit) via 3b928ed5ed7e93144714fbe4e332ef04769d0b08 (commit) via 34287fbf01125845844f84de7e6111e77d137775 (commit) via 120250ad6fe8d2b641b716d5b37d48b125db23ca (commit) via 306bb993aab07f115ff6cbc89d81f862e08f7c32 (commit) via 3e4e58f349c201a2ed02971ef95051773fcef39b (commit) via 3ee67ff5c2f9da513c77b8ab9dfc0067296dadec (commit) via abb347853317427a227592c4fa4b38e99f9e7152 (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 (c11f61401664eb9bb8282445356f5ca851ac1265) \ N -- N -- N (1789a16e884fa069bc2244791a4659c84efdffc8) 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=1789a16e884fa069bc2244791a4659c84... commit 1789a16e884fa069bc2244791a4659c84efdffc8 Author: Jacob Erlbeck <jerlbeck@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 - remove this commit Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=08001dc2d5c02f67622de15fe7b36bc6b... commit 08001dc2d5c02f67622de15fe7b36bc6b7098bda Author: Jacob Erlbeck <jerlbeck@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=83c92aca6904b44f129c3aa2dbced8cc0... commit 83c92aca6904b44f129c3aa2dbced8cc0bacea91 Author: Jacob Erlbeck <jerlbeck@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=3b928ed5ed7e93144714fbe4e332ef047... commit 3b928ed5ed7e93144714fbe4e332ef04769d0b08 Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Mon Jan 26 14:43:07 2015 +0100 sgsn: Add sgsn_mm_ctx_cleanup_free for safe shutdown Currently the MM context cleanup code is distributed over several functions. sgsn_mm_ctx_free not only frees data structure but also eventually stops the timer and does the subscriber clean-up. mm_ctx_cleanup_free (gprs_gmm.c) cleans up the PDP contexts and unassign the TLLI. This commit moves the cleanup code from both functions into a new unifying function sgsn_mm_ctx_cleanup_free that cares about the clean-up of all related sub-systems. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=34287fbf01125845844f84de7e6111e77... commit 34287fbf01125845844f84de7e6111e77d137775 Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Mon Jan 26 13:52:42 2015 +0100 sgsn: Don't allow mmctx == NULL in sgsn_update_subscriber_data Currently, sgsn_update_subscriber_data can be called with mmctx == NULL and will find and associate the right context (if present) based on the subscriber's IMSI. This will not happen in regular use any more, since sgsn_update_subscriber_data will only be called when subscribers are used (auth mode 'remote') and in this case gprs_subscr_get_or_create_by_mmctx will already be called by sgsn_auth_request. Therefore, MM context and subscriber are always associated except for some test cases and experimental VTY usage. The current implementation of sgsn_update_subscriber_data also causes additional complexity for the deletion on MM contexts to avoid a ipossible double-free MM contexts. This commit removes the MM context <-> subscriber association code from sgsn_update_subscriber_data. That function must always be called with mmctx != NULL, now. To avoid problems with VTY and test usage, the calling subscriber function now only call sgsn_update_subscriber_data when mmctx != NULL, since the purpose of that function is to update that state of an existing MM context after subscriber data has been changed. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: openbsc/src/gprs/gb_proxy_main.c | 2 +- openbsc/tests/sgsn/sgsn_test.c | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)