21 Nov
2017
21 Nov
'17
2:25 p.m.
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 "An utility library for Open Source Mobile Communications".
The branch, neels/sanitize has been updated
discards ea047967f3570a7a2ac5829295093b44723f0aca (commit)
discards cde83f76bba1ac91a54a24b2c48c740f2a39efa2 (commit)
discards 9488d4d54054538ea1d2d805f236dd21a668bbd3 (commit)
discards 66ee5a28b78e2c02186d51e527bdfd58853f082d (commit)
discards 7a4e2acb94f9223bd2b13dffbbea20b38b3f37cb (commit)
discards 0a08423fe76e949830c3e57c5dc6a0706dd99c8d (commit)
discards cdad4f6385494fe75b7e6226d29042ac2fe9f86e (commit)
discards b8fa9fd6cfb9e7d5d7dc010657b2850e9ecbd69a (commit)
discards fd7aa1bbbf83ef8ca7871430d2b82db7a4c02035 (commit)
discards b15d6aea96dfdd6e529c7fdd53434d27453f60ef (commit)
via 3f19ecfcbc6dfdbaa73c8552922361e812ff311a (commit)
via 5365c34564a673a108fb85e6f58a4be6944033d9 (commit)
via fe1ed39846c6537ebfe19d22500ee2e38587c143 (commit)
via e750980d6c89cf7052daa62745366a743badd384 (commit)
via 85f5a2cd9c46ffd165f9244b4e219bfc03aa5e0e (commit)
via cd325efae564384c74b4af6163303ddc81c7a3c1 (commit)
via 0128c78ffe25196f53fbbc0884a9c4587f493224 (commit)
via 9541a683780d23b260c5c0f6b9a9572a7ac16a66 (commit)
via 568f8e20175a21da4e4537a2f5a4f7fedec8c6d6 (commit)
via 10ee73a7b39b2867fde2a827b199f6264149c75c (commit)
via 3fad5d782acbd97be1124ccab874741261913429 (commit)
via abcd0e37b77529dadfc296cda7aacfe31858d74d (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 (ea047967f3570a7a2ac5829295093b44723f0aca)
\
N -- N -- N (3f19ecfcbc6dfdbaa73c8552922361e812ff311a)
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/libosmocore/commit/?id=3f19ecfcbc6dfdbaa73c85529223…
commit 3f19ecfcbc6dfdbaa73c8552922361e812ff311a
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Sat Nov 18 23:10:24 2017 +0100
fsm_tmr_cb: don't set T=0, the fi may no longer exist
When calling the timer_cb, that may have effected an fi termination and
deallocation, e.g. from dispatching events and/or complex choices made.
Current timer_cb implementations expect T to reflect the fired timer number, so
we can't actually set T=0 before calling the timer_cb.
Instead, never reset T to zero, let it always reflect the timer that last
fired. When a new timer starts, T will be set to its new value.
Adding a T arg to the timer_cb() would have been the cleanest solution, so that
fi->T can be set to zero before dispatching the timer_cb. But since we've
already rolled out this FSM API, we should stay backwards compatible.
In the case where the timer returned 1 to request termination, we can assume
that the fi still exists, but to be consistent, don't set T = 0 in that code
path either.
Change-Id: I18626b55a1491098b3ed602df1b331f08d25625a
http://cgit.osmocom.org/libosmocore/commit/?id=5365c34564a673a108fb85e6f58a…
commit 5365c34564a673a108fb85e6f58a4be6944033d9
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Sat Nov 18 23:07:38 2017 +0100
osmo_strlcpy: sanitize: don't memcpy from NULL src even if len is 0
Change-Id: I883048cf2807e606c6481634dbd569fc12aed889
-----------------------------------------------------------------------
Summary of changes:
TODO-RELEASE | 1 +
include/osmocom/core/msgb.h | 9 +++++++++
include/osmocom/vty/ports.h | 2 +-
src/fsm.c | 4 ++++
4 files changed, 15 insertions(+), 1 deletion(-)
hooks/post-receive
--
An utility library for Open Source Mobile Communications