[PATCH] Release lchan directly when refcount drops to zero

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/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Sun Nov 22 09:59:35 UTC 2009


Hi Holger,

On Fri, Nov 20, 2009 at 02:37:40PM +0100, Holger Freyther wrote:

> I'm not really following here. I have removed the lchan "auto release" timer 
> for now and directly release when the refcount drops down to zero. The only 
> timer that is active is the RSL timer we start in CHan ACTivate (or such).
> 
> For the CM Service Request... In the future this, Locationg Updating Request 
> and Paging Response (some more according to 08.08) would start the transaction 
> and we would keep the channel open as long as the transaction is alive.

yes, that sounds great and it is definitely how it should be.  But is this
already working with your proposed patch?

At least when I was trying last, simply reducing the timeout to 5 seconds
already made MO SMS fail.  If there meanwhile were some changes to the core
code that make it work: Great!

> We will introduce a "channel" leak only in the case where we will leak the 
> transaction. But this is a bug.

ok, that's fine with me.

> In any case I will try sending a real long SMS from my phone and try to 
> observe what is happening.

ok, thanks.
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list