netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hajime Tazaki <tazaki@wide.ad.jp>
To: kafai@fb.com
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
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	[thread overview]
Message-ID: <m26189tad2.wl@wide.ad.jp> (raw)
In-Reply-To: <20150504002938.GG2731450@devbig242.prn2.facebook.com>


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

  reply	other threads:[~2015-05-04  1:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 20:03 [PATCH net-next 0/5] ipv6: Stop /128 route from disappearing after pmtu update Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 1/5] ipv6: Consider RTF_CACHE when searching the fib6 tree Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 2/5] ipv6: Extend the route lookups to low priority metrics Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 3/5] ipv6: Stop /128 route from disappearing after pmtu update Martin KaFai Lau
2015-05-02 22:41   ` Hajime Tazaki
2015-05-02 23:20     ` Martin KaFai Lau
2015-05-03  0:19       ` Hajime Tazaki
2015-05-03  1:00         ` Martin KaFai Lau
2015-05-03  1:03           ` Martin KaFai Lau
2015-05-03 14:26           ` Hajime Tazaki
2015-05-03  3:38         ` Martin KaFai Lau
2015-05-03 14:29           ` Hajime Tazaki
2015-05-03 19:01             ` Martin KaFai Lau
2015-05-04  0:29               ` Martin KaFai Lau
2015-05-04  1:11                 ` Hajime Tazaki [this message]
2015-04-28 20:03 ` [PATCH net-next 4/5] ipv6: Stop rt6_info from using inet_peer's metrics Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 5/5] ipv6: Remove DST_METRICS_FORCE_OVERWRITE and _rt6i_peer Martin KaFai Lau
2015-05-02  1:01 ` [PATCH net-next 0/5] ipv6: Stop /128 route from disappearing after pmtu update David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m26189tad2.wl@wide.ad.jp \
    --to=tazaki@wide.ad.jp \
    --cc=Kernel-team@fb.com \
    --cc=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=kafai@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=shengyong1@huawei.com \
    --cc=steffen.klassert@secunet.com \
    --cc=yangyingliang@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).