openbsc.git branch zecke/features/osmux-reliability updated. 0.14.0-206-gc9923e4

gitosis at gitosis at
Sun Oct 4 09:23:51 UTC 2015

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, zecke/features/osmux-reliability has been updated
  discards  d35a8486742d7632c5f9ea8929ba5a68961411bb (commit)
       via  c9923e4e8a8752fe084fbf2bdb6c0755c11fed2e (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 (d35a8486742d7632c5f9ea8929ba5a68961411bb)
             N -- N -- N (c9923e4e8a8752fe084fbf2bdb6c0755c11fed2e)

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 -----------------------------------------------------------------

commit c9923e4e8a8752fe084fbf2bdb6c0755c11fed2e
Author: Holger Hans Peter Freyther <holger at>
Date:   Sun Oct 4 11:11:11 2015 +0200

    osmux: Remember the allocated CID and make sure it is released
    There appears to be a leak of CIDs:
     <000b> mgcp_osmux.c:544 All Osmux circuits are in use!
    There are paths that a CID had been requested and never released
    of the NAT. Remember the allocated CID inside the endpoint so it
    can always be released. It is using a new variable as the behavior
    for the NAT and MGCP MGW is different.
    Fixes: OW#1493


Summary of changes:

The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

More information about the osmocom-commitlog mailing list