From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH] ipv4: properly update pmtu Date: Wed, 22 Aug 2012 12:21:13 +0200 Message-ID: <1345630873.5158.970.camel@edumazet-glaptop> References: <1345618109.5158.599.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: David Miller , netdev , Julian Anastasov To: Sylvain Munaut Return-path: Received: from mail-bk0-f46.google.com ([209.85.214.46]:64995 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756999Ab2HVKVT (ORCPT ); Wed, 22 Aug 2012 06:21:19 -0400 Received: by bkwj10 with SMTP id j10so231025bkw.19 for ; Wed, 22 Aug 2012 03:21:17 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 2012-08-22 at 12:16 +0200, Sylvain Munaut wrote: > Hi, > > > From: Eric Dumazet > > > ip_rt_update_pmtu() calls dst_set_expires() to rearm a new expiration, > > but dst_set_expires() does nothing because dst.expires is already set. > > > > It seems we want to set the expires field to a new value, regardless > > of prior one. > > > > With help from Julian Anastasov. > > > > Reported-by: Sylvain Munaut > > Signed-off-by: Eric Dumazet > > CC: Julian Anastasov > > Tested-by: Sylvain Munaut > > I confirm this corrects the issue for me. I tested this on 3 machines > with 2 different hw config that all previously exhibited the issue > short after boot and now they've been running with this version of the > patch for hours without problems. > > @Eric: Thanks for looking into this. Thans Sylvain for being an early tester of bleeding edge kernel !