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 "UNNAMED PROJECT". The branch, jerlbeck/wip/ms-struct has been updated discards ec1ad5b8474a9a62724f2c6168d2cdc51d21364d (commit) discards 2e6c43bb2ac719c5a42ca5207f3d3ee831c5ed59 (commit) discards 072ac71c072f7d67a1a259d54daded95820dbaf4 (commit) discards 141390fcc3b55a5a0a5b08b5ee60b5ac9a9ec24e (commit) discards e934a4510e6b3a12807ebe9d7ef6bc5d2a16123e (commit) discards 963800da8a4b8bcda919e9c9da516f1633bedc9d (commit) via 49a74d4fabc9428e68c65f5be76d4b81ef76bbc3 (commit) via 4a8b3daf03a545a8eeba939439f21a988a66cc06 (commit) via ddf0682a6dedd1c2753b2b320ae5b343a6daeb25 (commit) via cbe17bbd38fa023d5670f50b03d127e189cf5664 (commit) via 754cb8816da6828ad2faf2deefc4ee1fe1eb9d6f (commit) via 4a643bfab1145316585f1a376f65695f16ed2ef4 (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 (ec1ad5b8474a9a62724f2c6168d2cdc51d21364d) \ N -- N -- N (49a74d4fabc9428e68c65f5be76d4b81ef76bbc3) 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/osmo-pcu/commit/?id=49a74d4fabc9428e68c65f5be76d4b8… commit 49a74d4fabc9428e68c65f5be76d4b81ef76bbc3 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Mon May 18 15:21:36 2015 +0200 tbf: Just pass the MS object in reuse_tbf Currently the MS will be searched based on the TLLI in resue_tbf(). Since the MS object is already known in the TBF when the TLLI is set, it can just be passed to the new TBF. This commit removes the call to update_ms() and just adds new_tbf->set_ms(ms()) which will also work as expected if ms() == NULL. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=4a8b3daf03a545a8eeba939439f21a9… commit 4a8b3daf03a545a8eeba939439f21a988a66cc06 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Mon May 18 14:35:11 2015 +0200 tbf: Explicitly pass the direction to update_ms() The type of the TBF update_ms() is being called on does not always reflect whether the TLLI has been signaled by the MS or the SGSN. This commit adds an additional parameter to tell the method, in which direction the TLLI has been passed. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=ddf0682a6dedd1c2753b2b320ae5b34… commit ddf0682a6dedd1c2753b2b320ae5b343a6daeb25 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Mon May 18 11:56:50 2015 +0200 tbf: Get the TLLI from the MS object Since the synchronisation of the TBF's concerning the TLLIs has been removed in 'Support new and old TLLI's', gprs_rlcmac_tbf::tlli() can return the old TLLI which is probably different to ms()->tlli() in that case. This can lead to a wrong TLLI being used in BSSGP messages. This commit modifies the TBF's tlli() method to get the current TLLI from the MS object. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=cbe17bbd38fa023d5670f50b03d127e… commit cbe17bbd38fa023d5670f50b03d127e189cf5664 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 15 15:50:43 2015 +0200 ms: Support new and old TLLIs According to the specification (GSM 04.08/24.008, 4.7.1.5) after a new P-TMSI has been assigned, the old P-TMSI must be kept basically until it has been used by both sides. Since the TLLI will be derived from the P-TMSI, the old TLLI must also be kept until the new TLLI has been used by both MS and SGSN. This commit modifies the TLLI handling of GprsMs accordingly. set_tlli() is only used with TLLIs derived from MS messages, confirm_tlli() is used with TLLIs derived from messages received from the SGSN. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=754cb8816da6828ad2faf2deefc4ee1… commit 754cb8816da6828ad2faf2deefc4ee1fe1eb9d6f Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 13 13:33:12 2015 +0200 ms: Integrate the MS storage Use the MS storage to find a MS object for a given TLLI instead of searching the TBF lists. The TBFs are then taken from the MS object, if one has been found. If all TBF might be temporarily detached from the MS object, a GprsMs::Guard is added to prevent the deletion of the object, in case another TBF gets attached later on in the scope. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=4a643bfab1145316585f1a376f65695… commit 4a643bfab1145316585f1a376f65695f16ed2ef4 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Tue May 12 17:54:33 2015 +0200 ms: Add MS storage class Currently the MS objects are contained in the TBF objects only. To allow for an extended life time after the TBF objects have been freed and to find them based on TLLI, a container for the MS objects is needed. This commit adds the container class and also adds the corresponding m_list member to GprsMs. Further integration into the PCU code is not yet done. Ticket: #1674 Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/gprs_ms_storage.cpp | 4 ++-- src/gprs_ms_storage.h | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- UNNAMED PROJECT