bluetooth: Fix potential assertion failure if MTU changes
authorMikel Astiz <mikel.astiz@bmw-carit.de>
Thu, 24 Jan 2013 09:16:56 +0000 (10:16 +0100)
committerTanu Kaskinen <tanuk@iki.fi>
Thu, 24 Jan 2013 13:55:31 +0000 (15:55 +0200)
commit132814f1148e6212cf594f918a1b91868425d387
tree8744246d779516bccce5699bb36d3e42cc9b12ee
parent707af43daa226d1b6c035abad0680bc70e7aaae0
bluetooth: Fix potential assertion failure if MTU changes

The assertion in hsp_process_render() assumes that, if a memory block is
already set by the time the function is reached, its size matches
write_block_size.

This can however fail if a transport has been released and acquired
back, in the unlikely case where the MTU has changed in the meantime,
assuming the memory block wasn't released.
src/modules/bluetooth/module-bluetooth-device.c