tree 0e2cbae6d327c6a2a0904f0ba95dcbde914a3d47
parent e75de4fa41d810113cf81f658a56e3972c7c12b4
author Antonio Quartulli <antonio@open-mesh.com> 1375215384 +0200
committer Antonio Quartulli <antonio@meshcoding.com> 1382196716 +0200

batman-adv: lock around TT operations to avoid sending inconsistent data

A TT response may be prepared and sent while the local or
global translation table is getting updated.

The worst case is when one of the tables is accessed after
its content has been recently updated but the metadata
(TTVN/CRC) has not yet. In this case the reader will get a
table content which does not match the TTVN/CRC.
This will lead to an inconsistent state and so to a TT
recovery.

To avoid entering this situation, put a lock around those TT
operations recomputing the metadata and around the TT
Response creation (the latter is the only reader that
accesses the metadata together with the table).

Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>