From: "Timo Teräs" <timo.teras@iki.fi>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] [IPV4]: Update MTU to all related cache entries in ip_rt_frag_needed()
Date: Sun, 27 Apr 2008 11:35:42 +0300 [thread overview]
Message-ID: <48143ADE.40304@iki.fi> (raw)
In-Reply-To: <20080426.232756.259679168.davem@davemloft.net>
David Miller wrote:
> From: Timo_Teräs <timo.teras@iki.fi>
> Date: Thu, 24 Apr 2008 13:05:27 +0300
>
>> Add struct net_device parameter to ip_rt_frag_needed() and update MTU to
>> cache entries where ifindex is specified. This is similar to what is
>> already done in ip_rt_redirect().
>>
>> Signed-off-by: Timo Teras <timo.teras@iki.fi>
>
> I haven't forgotten about this patch, I'm just still thinking about
> possible negative side effects. I don't think there are any, but
> I want to be sure.
>
> This function has been a constant source of consternation. It also
> doesn't do the right thing when the TOS is modified mid-network, and
> that's arguably wrong too but more difficult to solve efficiently than
> this ifindex keying case.
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.
Cheers,
Timo
next prev parent reply other threads:[~2008-04-27 8:35 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 [this message]
2008-04-29 10:32 ` 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=48143ADE.40304@iki.fi \
--to=timo.teras@iki.fi \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).