libosmocore.git branch neels/sanitize updated. 0.10.2-27-gea047967

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.org
Sun Nov 19 11:58:05 UTC 2017


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  467559c0bde2d79d369dd6fae0676b6e6b9dfdc1 (commit)
  discards  140ad0657e8cdcd650d5f23f917b9bc740cccec3 (commit)
  discards  d390a2cfcd30194a6d883ee55e57570b47aa0485 (commit)
  discards  c69a9f2724a3d79e061ef600ac186a93aac9d04a (commit)
  discards  d14112a98534350275b18af704267f05b20c32fa (commit)
  discards  213e5185c321d626ea9f9b5d357b5c773fdb1eb5 (commit)
  discards  6662784105e9cf7b6dbd0cce26e962388336d1aa (commit)
  discards  a6a0519b22ed28a90b26eb8ac9076067372fd07c (commit)
  discards  cbfdcddfa9b2cd0e8eab3a27a87d8d9e04c03dd5 (commit)
  discards  1470b59d2031378fbdf9a70055f5a48343ae62b7 (commit)
  discards  83b3afbf22491e8ae1e709e430326aef4bdbca68 (commit)
  discards  e311004eb40ecada318356955fd1e24e132a8649 (commit)
  discards  3e098c78aaf81e1de92360fb99768587bcdb6929 (commit)
  discards  0083c2433b03f47b95c1ac39c3ef6beaef051fd0 (commit)
  discards  a3584bf13467d79a681fbef8508759362e001986 (commit)
       via  ea047967f3570a7a2ac5829295093b44723f0aca (commit)
       via  cde83f76bba1ac91a54a24b2c48c740f2a39efa2 (commit)
       via  9488d4d54054538ea1d2d805f236dd21a668bbd3 (commit)
       via  66ee5a28b78e2c02186d51e527bdfd58853f082d (commit)
       via  7a4e2acb94f9223bd2b13dffbbea20b38b3f37cb (commit)
       via  0a08423fe76e949830c3e57c5dc6a0706dd99c8d (commit)
       via  cdad4f6385494fe75b7e6226d29042ac2fe9f86e (commit)
       via  b8fa9fd6cfb9e7d5d7dc010657b2850e9ecbd69a (commit)
       via  fd7aa1bbbf83ef8ca7871430d2b82db7a4c02035 (commit)
       via  b15d6aea96dfdd6e529c7fdd53434d27453f60ef (commit)
       via  9a938ae882a4d21f132291136c92d5311b84d7e2 (commit)
       via  d8e79c7fff7f1b004551589a0eb32026e5cba812 (commit)
       via  dd2456043348cbfb9fb81fd88e33c6864d718cee (commit)
       via  39720acb069a33dfef77f07044efe89d0327d963 (commit)
       via  00393e1a042df7d8d5fc59d6443502b6bd82c520 (commit)
       via  b93f60f7cd4bebbe6c26a456ea0b394fcafc731f (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 (467559c0bde2d79d369dd6fae0676b6e6b9dfdc1)
            \
             N -- N -- N (ea047967f3570a7a2ac5829295093b44723f0aca)

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

commit ea047967f3570a7a2ac5829295093b44723f0aca
Author: Neels Hofmeyr <neels at 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=cde83f76bba1ac91a54a24b2c48c740f2a39efa2

commit cde83f76bba1ac91a54a24b2c48c740f2a39efa2
Author: Neels Hofmeyr <neels at 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:
 configure.ac             |  2 +-
 m4/ax_check_simd.m4      | 18 +++++++++---------
 src/Makefile.am          | 10 +++++-----
 src/conv_acc.c           | 24 ++++++++++++------------
 src/conv_acc_sse.c       |  2 +-
 src/conv_acc_sse_avx.c   |  2 +-
 src/fsm.c                |  5 +----
 src/rate_ctr.c           | 25 ++++++++++---------------
 src/utils.c              |  3 ++-
 tests/stats/stats_test.c | 17 ++++-------------
 10 files changed, 46 insertions(+), 62 deletions(-)


hooks/post-receive
-- 
An utility library for Open Source Mobile Communications



More information about the osmocom-commitlog mailing list