This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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, neels/gtphub has been updated
discards b599a1ca083c92b81f5e340def6ea4ca06ad9f55 (commit)
discards 4aedfc2d688510d572e6553334f5830afd9ba80b (commit)
via 2170bf7b26f835d19ffd2ddbb7af3c687c5aedae (commit)
via dc2daa1da714bc28e0779e8b9fb6961904a8e616 (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 (b599a1ca083c92b81f5e340def6ea4ca06ad9f55)
\
N -- N -- N (2170bf7b26f835d19ffd2ddbb7af3c687c5aedae)
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=2170bf7b26f835d19ffd2ddbb7af3c687c5aedae
commit 2170bf7b26f835d19ffd2ddbb7af3c687c5aedae
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date: Mon Dec 7 01:13:47 2015 +0100
gtphub: add VTY show for peers and peer stats.
http://cgit.osmocom.org/openbsc/commit/?id=dc2daa1da714bc28e0779e8b9fb6961904a8e616
commit dc2daa1da714bc28e0779e8b9fb6961904a8e616
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date: Sun Dec 6 23:12:02 2015 +0100
gtphub: improve handling of restarted peer.
Handle peer restart earlier, so that all the tunnels are deleted by the restart
code path, instead of the first one being deleted due to reused TEI. That
caused confusing logging messages.
Also, when receiving Delete confirmations from the peer that didn't restart,
don't complain about unknown peer, but acknowledge and remove the half
invalidated tunnel. This means that the pending delete entry from the restart
code path is not needed / not used, so don't bother to add pending delete
entries upon peer restart.
The test test_peer_restarted_reusing_tei() hits the situation where a tunnel is
removed because of a reused TEI rather than the restart counter. Adjust the
test to expect the "out-of-band" delete request earlier on, and to still see
the half invalidated tunnel around. Enhance the test by adding the delete
response from the peer that didn't restart, and add a final tunnels_are()
verification.
Sponsored-by: On-Waves ehi
pd
-----------------------------------------------------------------------
Summary of changes:
openbsc/src/gprs/gtphub.c | 8 --------
1 file changed, 8 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)