{"push_id":540234486,"size":1,"distinct_size":1,"ref":"refs/heads/lp5.0-pb","head":"9b87162abf6b92b2356ee9fb9218121df8dfaed7","before":"78d9fce0e4fe55bd9fef8f57d37bdfcd646c1265","commits":[{"sha":"9b87162abf6b92b2356ee9fb9218121df8dfaed7","author":{"email":"55346d3bc0c58d58503ceaa50b259ca76fcb3262@ms2.inr.ac.ru","name":"Alexey Kuznetsov"},"message":"tcp: resets are misrouted\n\n[ Upstream commit 4c67525849e0b7f4bd4fab2487ec9e43ea52ef29 ]\n\nAfter commit e2446eaa (\"tcp_v4_send_reset: binding oif to iif in no\nsock case\").. tcp resets are always lost, when routing is asymmetric.\nYes, backing out that patch will result in misrouting of resets for\ndead connections which used interface binding when were alive, but we\nactually cannot do anything here.  What's died that's died and correct\nhandling normal unbound connections is obviously a priority.\n\nComment to comment:\n> This has few benefits:\n>   1. tcp_v6_send_reset already did that.\n\nIt was done to route resets for IPv6 link local addresses. It was a\nmistake to do so for global addresses. The patch fixes this as well.\n\nActually, the problem appears to be even more serious than guaranteed\nloss of resets.  As reported by Sergey Soloviev <sol@eqv.ru>, those\nmisrouted resets create a lot of arp traffic and huge amount of\nunresolved arp entires putting down to knees NAT firewalls which use\nasymmetric routing.\n\nChange-Id: Id7ff4096cb61ad42cf1a3513a15a5a3f006c622b\nSigned-off-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AICP/kernel_htc_endeavoru/commits/9b87162abf6b92b2356ee9fb9218121df8dfaed7"}]}