From: Simeon Penev <spenev@istac.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Patch for MTU in the routing table cache
Date: Fri, 02 Mar 2012 14:49:21 +0100 [thread overview]
Message-ID: <4F50CFE1.5040605@istac.de> (raw)
In-Reply-To: <1330695791.2469.17.camel@edumazet-laptop>
Hi Eric,
no, i didn't. I'm new to the developer list and just wanted to post a
patch proposition. I hoped that the maintainer of the code (probably
Alan Cox) will decide whether to use it.
Best regards,
Simeon
On 03/02/2012 02:43 PM, Eric Dumazet wrote:
> Le vendredi 02 mars 2012 à 14:13 +0100, Simeon Penev a écrit :
>> Hi,
>>
>> after testing the new 3.2 kernel and the new route caching code, i've
>> found a bug in net/ipv4/route.c. The route cache does not detect changes
>> to the MTU of the interface. Therefore IP fragmentation will happen with
>> false MTU. Please see attached the proposed patch.
>>
> Hi
>
> Did you test this patch doesnt break things like
>
> ip ro add 96.17.148.89 via 10.0.0.1 mtu 800
>
> (and keep eth0 mtu being standard mtu)
>
>
>
>
next prev parent reply other threads:[~2012-03-02 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 13:13 Patch for MTU in the routing table cache Simeon Penev
2012-03-02 13:43 ` Eric Dumazet
2012-03-02 13:49 ` Simeon Penev [this message]
2012-03-02 14:27 ` Eric Dumazet
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=4F50CFE1.5040605@istac.de \
--to=spenev@istac.de \
--cc=eric.dumazet@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.