stable.vger.kernel.org archive mirror
 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: Wed, 22 May 2019 19:29:45 +0200	[thread overview]
Message-ID: <20190522172945.GA25977@kroah.com> (raw)
In-Reply-To: <84edd412-c07d-28be-1723-a4727ae2ea56@gmail.com>

On Wed, May 22, 2019 at 10:52:57AM -0600, David Ahern wrote:
> On 5/22/19 10:51 AM, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.14-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> As I recall it only needs to go back to 4.17.

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.

thanks,

greg k-h

  reply	other threads:[~2019-05-22 17:29 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 [this message]
2019-05-22 17:36     ` David Ahern
2019-05-23  5:42       ` Greg KH

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=20190522172945.GA25977@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 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).