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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".

The branch, zecke/stable/0.15 has been created at 95cce409584a0543f982df7e997720a3054d456d (commit)

- Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=95cce409584a0543f982df7e997720a30...

commit 95cce409584a0543f982df7e997720a3054d456d Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Thu May 26 14:34:02 2016 +0200

debian: Make a new release for better memory mgmt

Puts the copied IMSI into the right context to be released at the SCCP connection level.

Change-Id: Ibbe8fc969393e503780933a962ad35dc215cb5e7

http://cgit.osmocom.org/openbsc/commit/?id=92f089732148bd6676d9663ed14d1c079...

commit 92f089732148bd6676d9663ed14d1c0799284b73 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Mon May 23 17:58:03 2016 +0200

filter/nat: Fix the context for the imsi assignment

In c09f8a3b7fb94ccef41e33c32bfe2bff1ffe0e44 as part of a cleanup I accidently changed the talloc context from "con" to "bsc". The issue occurred at an earlier commit when assigning req.ctx to the "wrong" context. The allocation needs to be scoped by the struct nat_sccp_connection and not the connection from BSC to NAT.

Before we have a nat_sccp_connection we scope the copied imsi to the bsc_connection and then steal it, but for the identity resp we will always have a nat_sccp_connection and can already use the right context.

[Backported from master]

Change-Id: I53789aad2809e19338ad3b2deb72c4757e7bd524 Related: OS#1733 Reviewed-on: https://gerrit.osmocom.org/102 Tested-by: Jenkins Builder Reviewed-by: Harald Welte laforge@gnumonks.org Reviewed-by: daniel dwillmann@sysmocom.de Reviewed-by: Holger Freyther holger@freyther.de

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

hooks/post-receive