summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorTuong Lien <tuong.t.lien@dektech.com.au>2019-08-15 10:24:08 +0700
committerDavid S. Miller <davem@davemloft.net>2019-08-16 16:27:13 -0700
commit712042313b23b5df7451faf4b279beb3025e990c (patch)
tree907be3ce9063e05a8375baa21bd9e07c951cfab1 /crypto
parentb9cbf8a64865b50fd0f4a3915fa00ac7365cdf8f (diff)
downloadlinux-712042313b23b5df7451faf4b279beb3025e990c.tar.bz2
tipc: fix false detection of retransmit failures
This commit eliminates the use of the link 'stale_limit' & 'prev_from' (besides the already removed - 'stale_cnt') variables in the detection of repeated retransmit failures as there is no proper way to initialize them to avoid a false detection, i.e. it is not really a retransmission failure but due to a garbage values in the variables. Instead, a jiffies variable will be added to individual skbs (like the way we restrict the skb retransmissions) in order to mark the first skb retransmit time. Later on, at the next retransmissions, the timestamp will be checked to see if the skb in the link transmq is "too stale", that is, the link tolerance time has passed, so that a link reset will be ordered. Note, just checking on the first skb in the queue is fine enough since it must be the oldest one. A counter is also added to keep track the actual skb retransmissions' number for later checking when the failure happens. The downside of this approach is that the skb->cb[] buffer is about to be exhausted, however it is always able to allocate another memory area and keep a reference to it when needed. Fixes: 77cf8edbc0e7 ("tipc: simplify stale link failure criteria") Reported-by: Hoang Le <hoang.h.le@dektech.com.au> Acked-by: Ying Xue <ying.xue@windriver.com> Acked-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: Tuong Lien <tuong.t.lien@dektech.com.au> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions