tree 4f97c73c68d46a2b75138a0be00ea3ba3dd881c6
parent d6b62e3a8c239e0646d33720d58f7ff6dc875d2b
author Harald Welte <laforge@gnumonks.org> 1273687825 +0000
committer Harald Welte <laforge@gnumonks.org> 1273688575 +0200

Gb Proxy: Proper msgb memory management

The old idea was to take a msgb from gbprox_rcvmsg() and then
modify it and finally send it all the way down to nsip_sendmsg()
to the remote peer.

However, this introduces memory management difficulties, as we then
have to distinguish three cases:
 * msgb was sent to a remote peer
 * we sent some error message and need to free the msgb
 * we need to make n-1 copies in case of a BSSVC-RESET from the SGSN

So instead we now simply always copy the message if we pass it on.

All messages received by gbprox_rcvmsg() are msgb_free()d in the very
same routine

All messages allocated by tx2peer() or tx2sgsn() are freed after
nsip_sendmsg()