From: Ben Hutchings <ben@decadent.org.uk>
To: Yura Pakhuchiy <pakhuchiy@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: Per route MTU settings are broken in linux kernel 3.2
Date: Wed, 26 Jun 2013 02:12:26 +0100 [thread overview]
Message-ID: <1372209146.4006.35.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1372079315.32157.15.camel@linux>
[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]
On Mon, 2013-06-24 at 20:08 +0700, Yura Pakhuchiy wrote:
> On Mon, 2013-06-24 at 13:45 +0100, Ben Hutchings wrote:
> > On Mon, 2013-06-24 at 15:44 +0700, Yura Pakhuchiy wrote:
> > > Hello Ben,
> > >
> > > Looks like setting per route MTU (as described in [1]) is broken in
> > > Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
> > > looks like problem is fixed there. I filled Ubuntu bug report [2] with
> > > more details and sample script which illustrates problem. But since this
> > > problem is probably also present in stock kernel (not just in Ubuntu),
> > > is it possible to backport fixes to stable 3.2 series?
> > >
> > > 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
> > > 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507
> >
> > Sure, what are the fixes?
>
> Actually, I do not know :-( Ubuntu devs have not fixed this problem in
> Ubuntu 3.2 kernel. But these commits in mainline kernel looks related:
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9b04f350057863d1fad1ba071e09362a1da3503e
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=5f2d04f1f9b52604fca6ee08a77972c0df67e082
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=d851c12b60471188e15e5c8405b289073e8dd025
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=7f92d334ba19a0d8e96f8f8f092219553367d921
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=ee9a8f7ab2edf801b8b514c310455c94acc232f6
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=38d523e2948162776903349c89d65f7b9370dadb
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=fa1e492aa3cbafba9f8fc6d05e5b08a3091daf4a
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=05ab86c55683410593720003442dde629782aaac
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9cb3a50c5f63ed745702972f66eaee8767659acd
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=b44108dbdbaa07c609bb5755e8dd6c2035236251
>
> However I'm not sure whether they all are required or sufficient to fix
> everything correctly.
Sorry, but I really do need someone to tell me exactly what's required.
I'm not likely to find the time to work this out myself.
Ben.
--
Ben Hutchings
Knowledge is power. France is bacon.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-06-26 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 8:44 Yura Pakhuchiy
2013-06-24 12:45 ` Ben Hutchings
2013-06-24 13:08 ` Yura Pakhuchiy
2013-06-26 1:12 ` Ben Hutchings [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=1372209146.4006.35.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pakhuchiy@gmail.com \
--cc=stable@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
all inboxes | Powered by JetHome®