stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Martin KaFai Lau <kafai@fb.com>
Cc: netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Hannes Frederic Sowa <hannes@stressinduktion.org>,
	Julian Anastasov <ja@ssi.bg>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Kernel Team <Kernel-team@fb.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception
Date: Fri, 28 Aug 2015 11:27:35 +0200	[thread overview]
Message-ID: <55E02987.8040908@ahsoftware.de> (raw)
In-Reply-To: <20150828073429.GA67211@kafai-mba.gkf168.com>

Am 28.08.2015 um 09:36 schrieb Martin KaFai Lau:
> On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote:
>> That's why I vote to check out if it's possible/reasonable to backport this
>> series to the stable kernels.
> I have backported to 4.0.y without major issue, so possible.

Sure, as this was likely one of the versions they've used to create the 
patch.

> I did try on 3.1x and gave up.
>
> It is a lot of changes,  so I don't think it is a good idea for -stable.

Depends on what you're expecting from a (stable) kernel.

The patch description mentions what happens when a system deals with a 
lot of other ipv6-systems and that problem is easy to exercise and to value.

Rating the information leak is harder, some people even won't understand 
that this might be a problem.

And now look at which kernel-versions are now used in new devices 
(likely something <= 3.10, which is more than two years old), how long 
they will be used, and make a guess about IPv6 usage in 5 years.

Anyway, I've no insights about all the politics happening in the 
background (e.g. stuff like the LTSI tree) and I've just wanted raise 
awareness about that (imho important) patch series.

Regards,

Alexander Holler

  reply	other threads:[~2015-08-28  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1432353366-2296465-1-git-send-email-kafai@fb.com>
     [not found] ` <55B89C14.2070700@ahsoftware.de>
     [not found]   ` <55BA1144.9090203@ahsoftware.de>
2015-08-15  7:48     ` [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception Alexander Holler
2015-08-17  9:43       ` Alexander Holler
2015-08-28  7:36         ` Martin KaFai Lau
2015-08-28  9:27           ` Alexander Holler [this message]
2015-08-28  9:34             ` Alexander Holler
2015-08-28 18:27           ` 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=55E02987.8040908@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=Kernel-team@fb.com \
    --cc=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=ja@ssi.bg \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /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).