Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: Sylvain Munaut <s.munaut@whatever-company.com>, netdev@vger.kernel.org
Subject: Re: IP fragmentation broken in 3.6-rc ?
Date: Tue, 21 Aug 2012 18:47:13 +0200	[thread overview]
Message-ID: <1345567633.5158.534.camel@edumazet-glaptop> (raw)
In-Reply-To: <alpine.LFD.2.00.1208211815550.2149@ja.ssi.bg>

On Tue, 2012-08-21 at 19:34 +0300, Julian Anastasov wrote:
> 	Hello,
> 
> On Tue, 21 Aug 2012, Eric Dumazet wrote:
> 
> > Following patch should help :
> > 
> > diff --git a/include/net/dst.h b/include/net/dst.h
> > index 621e351..a04aa37 100644
> > --- a/include/net/dst.h
> > +++ b/include/net/dst.h
> > @@ -435,7 +435,7 @@ static inline void dst_set_expires(struct dst_entry *dst, int timeout)
> >  	if (expires == 0)
> >  		expires = 1;
> >  
> 
> 	In theory, restart of PMTUD should not lead to
> fatal problems, we will get new MTUs. But with such
> change should be better, not much, because all MTU
> events will come at same time, later timer will expire
> and we will get again events from routers. The gain
> will be an increased period (with milliseconds to seconds)
> between PMTUD restarts. Compared to the 600-second timer,
> this should be gain below 1% in reduced traffic for PMTUD.
> Before now we started timer from first router, now we
> will start/update timer period after event from last router.
> 

Sorry I dont really understand what you mean


> 	But ipv4_link_failure and ip6_link_failure want to stop
> this timer by setting it to NOW (0). May be we have to add
> also a !timeout check here or to leave the code as before?
> 
> > -	if (dst->expires == 0 || time_before(expires, dst->expires))
> > +	if (dst->expires == 0 || time_after(expires, dst->expires))
> >  		dst->expires = expires;
> >  }
> 
> 	The original problem should be somewhere else, I think.

This patch fixed the problem for me.

My first patch was :

diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index e4ba974..9858714 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -956,6 +956,7 @@ static void ip_rt_update_pmtu(struct dst_entry *dst, struct sock *sk,
 		dst->obsolete = DST_OBSOLETE_KILL;
 	} else {
 		rt->rt_pmtu = mtu;
+		rt->dst.expires = 0;
 		dst_set_expires(&rt->dst, ip_rt_mtu_expires);
 	}
 }

  reply	other threads:[~2012-08-21 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 13:05 IP fragmentation broken in 3.6-rc ? Sylvain Munaut
2012-08-21 13:22 ` Eric Dumazet
2012-08-21 14:42   ` Eric Dumazet
2012-08-21 16:34     ` Julian Anastasov
2012-08-21 16:47       ` Eric Dumazet [this message]
2012-08-21 17:18         ` Julian Anastasov
2012-08-21 17:23           ` Eric Dumazet
2012-08-21 20:00             ` Julian Anastasov
2012-08-21 20:46               ` Eric Dumazet
2012-08-21 21:07                 ` Julian Anastasov
2012-08-21 17:44     ` Sylvain Munaut

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=1345567633.5158.534.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=ja@ssi.bg \
    --cc=netdev@vger.kernel.org \
    --cc=s.munaut@whatever-company.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