Subject: osmo-bts.git branch zecke/fixes/crash-on-release updated. 0.3.0-69-g45a160b
From: [email-masked]
To: [email-masked]
Date: Tue, 5 Nov 2013 15:20:21 GMT

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 "Osmocom BTS-side code (Abis, scheduling, ...)".

The branch, zecke/fixes/crash-on-release has been updated
  discards  9ada86e5a3b410d2c791b474f61c31d2d2f78149 (commit)
       via  45a160ba933f4615f1d066fe2f22da0f43e8cc4c (commit)
       via  897f97f6329d46e21fc80ea4bb2dfbfc11cf8123 (commit)
       via  5eef61414a4beb0ba3043bca88d42b6ba68d8c70 (commit)
       via  5b69ec3e720d21753101c9a0e1a38d0926ba3854 (commit)
       via  08571b158835df3db09cc94686a8fe62d1845cc9 (commit)
       via  9ef742f5e751c1d5fdfae14aa663e6056e6cac6f (commit)
       via  f3108fafab3705752e21861a18c257c35e194c08 (commit)
       via  0133ff386646bf8b29075502f233f2641d51255a (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 (9ada86e5a3b410d2c791b474f61c31d2d2f78149)
            \
             N -- N -- N (45a160ba933f4615f1d066fe2f22da0f43e8cc4c)

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-bts/commit/?id=45a160ba933f4615f1d066fe2f22da0f43e8cc4c

commit 45a160ba933f4615f1d066fe2f22da0f43e8cc4c
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Fri Nov 1 18:22:43 2013 +0100

    bts: Fix crash of receiving data during the release process
    
    Release/Free the lapdm resources _after_ the channel has
    been fully released. Do not forward data unless the lchan
    is in the active state.
    
     (gdb) p lchan->state
     $4 = LCHAN_S_REL_REQ
     (gdb) bt
     #0  lapd_dl_flush_hist (dl=0x40454894) at lapd_core.c:164
     #1  0x44873b54 in lapd_rx_u (lctx=0xbe9bd5a8, msg=0x92f90) at lapd_core.c:1040
     #2  lapd_ph_data_ind (msg=0x92f90, lctx=0xbe9bd5a8) at lapd_core.c:1644
     #3  0x44876d50 in l2_ph_data_ind (link_id=<optimized out>, chan_nr=<optimized out>,
         le=<optimized out>, msg=0x92f90) at lapdm.c:637
     #4  lapdm_phsap_up (oph=<optimized out>, le=<optimized out>) at lapdm.c:707
     #5  0x0000c504 in handle_ph_data_ind (l1p_msg=0x97358, data_ind=0x97420, fl1=<optimized out>)
         at l1_if.c:774
     #6  l1if_handle_ind (fl1=<optimized out>, msg=0x97358) at l1_if.c:892

-----------------------------------------------------------------------

Summary of changes:
 include/osmo-bts/bts.h        |  8 +++++
 include/osmo-bts/oml.h        |  5 +++
 src/common/oml.c              |  5 +++
 src/osmo-bts-sysmo/femtobts.c | 21 +++++++++++
 src/osmo-bts-sysmo/femtobts.h |  1 +
 src/osmo-bts-sysmo/l1_if.c    | 84 +++++++++++++++++++++++++++++++++++++++++--
 src/osmo-bts-sysmo/l1_if.h    |  3 ++
 src/osmo-bts-sysmo/main.c     | 25 +++++++++++++
 src/osmo-bts-sysmo/oml.c      | 80 +++++++++++++++++++++++++++++++++++++++--
 9 files changed, 227 insertions(+), 5 deletions(-)

hooks/post-receive
-- 
Osmocom BTS-side code (Abis, scheduling, ...)