diff options
author | Simon Wunderlich <sw@simonwunderlich.de> | 2015-09-11 16:04:13 (GMT) |
---|---|---|
committer | Antonio Quartulli <a@unstable.cc> | 2015-12-16 07:17:09 (GMT) |
commit | 5a1dd8a4773d4c24e925cc6154826d555a85c370 (patch) | |
tree | 60e9944e19fe8b52ef0e63667eb8af7cb7b85662 /Documentation | |
parent | c05a57f6fb6f398cde873c5ebe13ae26b3843b7e (diff) | |
download | linux-5a1dd8a4773d4c24e925cc6154826d555a85c370.tar.xz |
batman-adv: lock crc access in bridge loop avoidance
We have found some networks in which nodes were constantly requesting
other nodes BLA claim tables to synchronize, just to ask for that again
once completed. The reason was that the crc checksum of the asked nodes
were out of sync due to missing locking and multiple writes to the same
crc checksum when adding/removing entries. Therefore the asked nodes
constantly reported the wrong crc, which caused repeating requests.
To avoid multiple functions changing a backbone gateways crc entry at
the same time, lock it using a spinlock.
Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
Tested-by: Alfons Name <AlfonsName@web.de>
Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch>
Signed-off-by: Antonio Quartulli <antonio@meshcoding.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions