bug introduced with cea194d90b11aff7fc289149e4c7f305fad3535a
In the current TT code, when a TT_Response containing a full table is received form an originator, the node first purges all the clients for that originator in the global translation-table and then merges the new received table. During the purging phase each client deletion is done by means of a call_rcu() invocation and at the end of this phase the global entry counter for that originator is set to 0. However the invoked rcu function decreases by one the global entry counter for that originator too and since the rcu invocation is likely to be postponed, the node will end up in first setting the counter to 0 and then decreasing it one by one for each deleted client.
This bug leads to having a wrong global entry counter for the related node, say X. Then when the node with the broken counter will answer to a TT_REQUEST on behalf of node X, it will create faulty TT_RESPONSE that will generate an unrecoverable situation on the node that asked for the full table recover.
The non-recoverability is given by the fact that the node with the broken counter will keep answering on behalf of X because its knowledge about X's state (ttvn + tt_crc) is correct.
To solve this problem the counter is not explicitly set to 0.
Signed-off-by: Antonio Quartulli ordex@autistici.org --- translation-table.c | 1 - 1 file changed, 1 deletion(-)
diff --git a/translation-table.c b/translation-table.c index a66c2dc..19d23b4 100644 --- a/translation-table.c +++ b/translation-table.c @@ -910,7 +910,6 @@ void tt_global_del_orig(struct bat_priv *bat_priv, } spin_unlock_bh(list_lock); } - atomic_set(&orig_node->tt_size, 0); orig_node->tt_initialised = false; }