All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Ahern <dsahern@gmail.com>
Cc: edumazet@google.com, davem@davemloft.net, kafai@fb.com,
	syzkaller@googlegroups.com, weiwan@google.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ipv6: prevent possible fib6 leaks" failed to apply to 4.14-stable tree
Date: Thu, 23 May 2019 07:42:45 +0200	[thread overview]
Message-ID: <20190523054244.GC16130@kroah.com> (raw)
In-Reply-To: <6081e160-5d74-0ec7-59cc-56cdecbaad41@gmail.com>

On Wed, May 22, 2019 at 11:36:45AM -0600, David Ahern wrote:
> On 5/22/19 11:29 AM, Greg KH wrote:
> > Thanks, but someone backported the commit mentioned in the Fixes line:
> > 	Fixes: 93531c674315 ("net/ipv6: separate handling of FIB entries from dst based routes")
> > 
> > to 4.14.y.  If it's really not relevant there, not a big deal, now
> > dropped.
> 
> 
> Just checked and that commit is not in 4.14 line.
> 
> It is one of like 90 other patches that actually depend on other changes
> in 4.15, 4.16. I can not imagine some poor soul backporting all of that
> to 4.14.

Argh, my scripts caught that the string "93531c674315" was included in
the changelog for 4.14.72, but the context of that was:
	- fib6_info_release was introduced upstream in 93531c674315
	  ("net/ipv6: separate handling of FIB entries from dst based
	  routes"), but is not present in stable kernels; 4.14.y relies
	  on dst_release/ ip6_rt_put/dst_release_immediate.

So this was my mistake, thanks for pointing it out.

greg k-h

      reply	other threads:[~2019-05-23  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 16:51 FAILED: patch "[PATCH] ipv6: prevent possible fib6 leaks" failed to apply to 4.14-stable tree gregkh
2019-05-22 16:52 ` David Ahern
2019-05-22 17:29   ` Greg KH
2019-05-22 17:36     ` David Ahern
2019-05-23  5:42       ` Greg KH [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=20190523054244.GC16130@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=kafai@fb.com \
    --cc=stable@vger.kernel.org \
    --cc=syzkaller@googlegroups.com \
    --cc=weiwan@google.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 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.