gprs_bssgp: bssgp_fc_in(): fix mem leak on queue overflow

All successful and all error code paths of bssgp_fc_in() free the msgb, except
the code path calling fc_enqueue() when the msg is dropped (due to queue being
full, or failure to allocate).

Callers could theoretically catch the -ENOSPC return value and discard the
msgb. However, in other code paths, a callback's return value is returned,
which is expected to free the msgb, so such callback would have to never return
-ENOSPC when it freed the msgb. Much simpler semantics would be to free the
msgb in every code path, no matter which kind of error occurred.

Who is currently calling bssgp_fc_in and how do they handle the return value?
- bssgp_fc_test.c ignores the return value (and hits a mem leak aka sanitizer
  build failure if the queue is full).
- fc_timer_cb() ignores the return value.
- bssgp_tx_dl_ud() returns the bssgp_fc_in() rc.
  - which is returned by a cascade of functions leading up to being returned,
    for example, by gprs_llgmm_reset(), which is usually called with ignored
    return code.
At this point it is already fairly clear that bssgp_fc_in() should always free
the msgb, since the callers don't seem to distinguish even between error or
success, let alone between -ENOSPC or other errors.

bssgp_fc_test: assert that no msgbs remain unfreed after the tests.
Adjust expected results.

Helps fix sanitizer build on debian 9.

Change-Id: I00c62a104baeaad6a85883c380259c469aebf0df
This commit is contained in:
Neels Hofmeyr 2017-11-16 22:32:36 +01:00
parent 0128c78ffe
commit cd325efae5
3 changed files with 9 additions and 4 deletions

View File

@ -764,7 +764,11 @@ int bssgp_fc_in(struct bssgp_flow_control *fc, struct msgb *msg,
}
if (bssgp_fc_needs_queueing(fc, llc_pdu_len)) {
return fc_enqueue(fc, msg, llc_pdu_len, priv);
int rc;
rc = fc_enqueue(fc, msg, llc_pdu_len, priv);
if (rc)
msgb_free(msg);
return rc;
} else {
/* record the time we transmitted this PDU */
osmo_gettimeofday(&time_now, NULL);

View File

@ -190,7 +190,8 @@ int main(int argc, char **argv)
printf("msgb ctx: %zu b in %zu blocks (0 b in 1 block == just the context)\n",
talloc_total_size(tall_msgb_ctx),
talloc_total_blocks(tall_msgb_ctx));
/* KNOWN BUG: expecting 0b in 1 block, but a full queue is still a mem leak */
OSMO_ASSERT(talloc_total_size(tall_msgb_ctx) == 0);
OSMO_ASSERT(talloc_total_blocks(tall_msgb_ctx) == 1);
talloc_free(tall_msgb_ctx);
printf("===== BSSGP flow-control test END\n\n");

View File

@ -56,7 +56,7 @@ size-max=100 oct, leak-rate=100 oct/s, queue-len=5 msgs, pdu_len=10 oct, pdu_cnt
30: FC OUT Nr 13
40: FC OUT Nr 14
50: FC OUT Nr 15
msgb ctx: 685 b in 6 blocks (0 b in 1 block == just the context)
msgb ctx: 0 b in 1 blocks (0 b in 1 block == just the context)
===== BSSGP flow-control test END
===== BSSGP flow-control test START
@ -229,6 +229,6 @@ size-max=100 oct, leak-rate=100 oct/s, queue-len=5 msgs, pdu_len=10 oct, pdu_cnt
30: FC OUT Nr 13
40: FC OUT Nr 14
50: FC OUT Nr 15
msgb ctx: 685 b in 6 blocks (0 b in 1 block == just the context)
msgb ctx: 0 b in 1 blocks (0 b in 1 block == just the context)
===== BSSGP flow-control test END