From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hajime Tazaki Subject: Re: [PATCH net-next 3/5] ipv6: Stop /128 route from disappearing after pmtu update Date: Mon, 04 May 2015 10:11:37 +0900 Message-ID: References: <1430251387-2942539-1-git-send-email-kafai@fb.com> <1430251387-2942539-4-git-send-email-kafai@fb.com> <20150502232040.GB2731450@devbig242.prn2.facebook.com> <20150503033801.GE2731450@devbig242.prn2.facebook.com> <20150503190108.GF2731450@devbig242.prn2.facebook.com> <20150504002938.GG2731450@devbig242.prn2.facebook.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: netdev@vger.kernel.org, hannes@stressinduktion.org, steffen.klassert@secunet.com, davem@davemloft.net, yangyingliang@huawei.com, shengyong1@huawei.com, Kernel-team@fb.com To: kafai@fb.com Return-path: Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]:36421 "EHLO mail.sfc.wide.ad.jp" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751755AbbEDBLm (ORCPT ); Sun, 3 May 2015 21:11:42 -0400 In-Reply-To: <20150504002938.GG2731450@devbig242.prn2.facebook.com> Sender: netdev-owner@vger.kernel.org List-ID: Hi Martin, At Sun, 3 May 2015 17:29:38 -0700, Martin KaFai Lau wrote: > On Sun, May 03, 2015 at 12:01:09PM -0700, Martin KaFai Lau wrote: > > Thanks for the details and confirming the last patch. I think I may > > know what could be wrong. I am going to confirm it first by trying > > to reproduce it. > I tried the sit and also the gre6 tunnel. I cannot make it break as > the way you have observed. The ping can still go through. I am probably > missing something. > > However, I did uncover a problem in this patch and posted a fix to > netdev. I have also attached here. Can you give it a try? tried it and it's perfect ! all other tests I have are also working fine. > If there is still no luck, do you have a chance to > reproduce it with a simple setup by iproute2 commands? > Can you specify which POINTTOPOINT device and sim device you are using? > Are they in or out of kernel-tree driver? indeed, it's an out-of-tree driver of LibOS patchset (*1) https://github.com/libos-nuse/net-next-nuse/blob/nuse/arch/lib/lib-device.c this is not always P2P device: an application (e.g., ns-3) can define the flags of the device. I'll follow up to reproduce with sit or gre and let you know once I got succeed. thank you. -- Hajime