tree 13cb8b344d71785d95fdd6cdb4ba0320b234a775
parent 956242dcec1bb61d46fe8214d3578dc769080ca9
author Pau Espin Pedrol <pespin@sysmocom.de> 1537180888 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> 1537184196 +0200

mgcp: Fix osmux_cid_bitmap static array size calculation

Right now it's not a big issue since OSMUX_CID_MAX is 255, so 255+1 is
256 which fits array boundaries correctly (multiple of 8). However, if
for example OSMUX_CID_MAX was modified to be 12, 12+1/8 = 1, so we'd
have an undesired memory access when accessing last 4 CIDs.

A +1 should be kept on top, because OSMUX_CID_MAX specified the maximum
number used by a CID, that is (0,OSMUX_CID_MAX), and as a result we
require OSMUX_CID_MAX+1 slots.

Change-Id: Iaf9b93712dbd2a862b01e70dd8e11893bfa6b24c