From: David Miller <davem@davemloft.net>
To: timo.teras@iki.fi
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] [IPV4]: Update MTU to all related cache entries in ip_rt_frag_needed()
Date: Tue, 29 Apr 2008 03:32:45 -0700 (PDT) [thread overview]
Message-ID: <20080429.033245.141337746.davem@davemloft.net> (raw)
In-Reply-To: <48143ADE.40304@iki.fi>
From: Timo_Teräs <timo.teras@iki.fi>
Date: Sun, 27 Apr 2008 11:35:42 +0300
> I understand your concern. It is pretty easy break routing cache with
> some seemingly unrelated changes. I tried to think about possible side
> effects, but concluded that this should be safe. Then again, I don't
> know all the tiny details and unusual scenarios. But I have been running
> a 2.6.23 kernel with (backported) patch on a production machine (router
> connected to two ISPs, internal subnet and also having multiple gre
> tunnels), so far I have not encountered any problems.
I thought more about your patch and it should be OK.
I've applied it, thanks a lot.
prev parent reply other threads:[~2008-04-29 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 10:05 [PATCH] [IPV4]: Update MTU to all related cache entries in ip_rt_frag_needed() Timo Teräs
2008-04-27 6:27 ` David Miller
2008-04-27 8:35 ` Timo Teräs
2008-04-29 10:32 ` David Miller [this message]
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=20080429.033245.141337746.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=timo.teras@iki.fi \
/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).