From mboxrd@z Thu Jan 1 00:00:00 1970 From: YueHaibing Subject: Re: net/arp: ARP cache aging failed. Date: Thu, 15 Dec 2016 10:58:55 +0800 Message-ID: <7a2e0ee3-e8db-0e5f-3d0d-64f6e6bf367c@huawei.com> References: <957c2a80-7302-1ce9-726e-1e7512a941f4@huawei.com> <1479902729.8455.479.camel@edumazet-glaptop3.roam.corp.google.com> <250d3a88-45ad-891f-389a-997f39d7bdad@stressinduktion.org> <1479944967.8455.516.camel@edumazet-glaptop3.roam.corp.google.com> <1fdf938e-600c-ce58-ece1-06b816ddba1c@stressinduktion.org> <40b84d35-4185-bfbc-7f85-9d6abf984d31@stressinduktion.org> <74d41c47-7091-3c52-096d-5b9af2e0e9cf@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Cc: Hannes Frederic Sowa , Eric Dumazet , "David S. Miller" , To: Julian Anastasov Return-path: Received: from szxga03-in.huawei.com ([119.145.14.66]:7431 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753214AbcLODAm (ORCPT ); Wed, 14 Dec 2016 22:00:42 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 2016/12/15 4:15, Julian Anastasov wrote: > > Hello, > > On Wed, 14 Dec 2016, YueHaibing wrote: > >> On 2016/11/26 4:40, Julian Anastasov wrote: >>> >>> So, the idea is to move TCP and other similar >>> users to the new dst_confirm_sk() method. If other >>> dst_confirm() users are left, they should be checked >>> if dsts with rt_gateway = 0 can be wrongly used. >> >> Sorry for so late. > > In fact, I'm late too because I almost finished > my changes, the only remaining part is the cxgb files... > >> Based on your ideas, I make a patch and test it for a while. > > The problem is that it is valid only for TCP. > Also, this flag should be reset sometimes, eg. when sk dst > changes... > >> It works for me. >> >> @@ -847,7 +847,7 @@ static int ping_v4_sendmsg(struct sock *sk, struct msghdr *msg, size_t len) >> return err; >> >> do_confirm: >> - dst_confirm(&rt->dst); >> + dst_confirm_sk(sk); > > MSG_CONFIRM from sendmsg needs special treatment. The > problem is that UDP sending does not lock the socket, so I also > added a skb flag to handle this situation in ip*_append_data. > We do not want threaded application firing at different > destinations to confirm the wrong neighbour. MSG_PROBE is > another issue, the XFRM dst chaining, etc... > > I hope, I'll be ready this weekend with few patches > that change all dst_confirm users... There I'll explain > everything in detail. > > Regards > > -- > Julian Anastasov > > . > Great, I'll be glad to do a testing.