stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: gregkh@linuxfoundation.org
Cc: dsahern@kernel.org, jonas.gorski@gmail.com, kuba@kernel.org,
	razor@blackwall.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ipv4: Fix route deletion when nexthop info is not specified" failed to apply to 6.0-stable tree
Date: Sun, 4 Dec 2022 09:14:44 +0200	[thread overview]
Message-ID: <Y4xI5C0bDilNwWm0@shredder> (raw)
In-Reply-To: <Y4tcuoEGHI92wF3u@shredder>

On Sat, Dec 03, 2022 at 04:27:06PM +0200, Ido Schimmel wrote:
> On Sat, Dec 03, 2022 at 12:00:01PM +0100, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.0-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>.
> > 
> > Possible dependencies:
> > 
> > d5082d386eee ("ipv4: Fix route deletion when nexthop info is not specified")
> > 61b91eb33a69 ("ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference")
> 
> Yes, this one is missing. Will send both.

Just saw the mail from Sasha. Looks like he already took care of it.
Both patches are in 6.0 queue:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.0/ipv4-handle-attempt-to-delete-multipath-route-when-f.patch
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.0/ipv4-fix-route-deletion-when-nexthop-info-is-not-spe.patch

Thanks

      reply	other threads:[~2022-12-04  7:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 11:00 FAILED: patch "[PATCH] ipv4: Fix route deletion when nexthop info is not specified" failed to apply to 6.0-stable tree gregkh
2022-12-03 14:27 ` Ido Schimmel
2022-12-04  7:14   ` Ido Schimmel [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=Y4xI5C0bDilNwWm0@shredder \
    --to=idosch@nvidia.com \
    --cc=dsahern@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonas.gorski@gmail.com \
    --cc=kuba@kernel.org \
    --cc=razor@blackwall.org \
    --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;
as well as URLs for NNTP newsgroup(s).