From: Greg KH <greg@kroah.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: stable@vger.kernel.org, Jiri Pirko <jiri@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.1.y] net: move altnames together with the netdevice
Date: Mon, 23 Oct 2023 09:41:53 +0200 [thread overview]
Message-ID: <2023102304-mortally-safely-9e86@gregkh> (raw)
In-Reply-To: <20231020222401.3438686-1-kuba@kernel.org>
On Fri, Oct 20, 2023 at 03:24:00PM -0700, Jakub Kicinski wrote:
> [ Upstream commit 8e15aee621618a3ee3abecaf1fd8c1428098b7ef ]
>
> The altname nodes are currently not moved to the new netns
> when netdevice itself moves:
Thanks for the backports, I took both of these instead of the more
complex patch chain that Sasha backported, as there were fixups for
those dependancies that didn't apply to the older kernels, and it was
just going to get to be too big of a mess to make sure everything was
correct over time.
greg k-h
prev parent reply other threads:[~2023-10-23 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 20:34 FAILED: patch "[PATCH] net: move altnames together with the netdevice" failed to apply to 6.1-stable tree gregkh
2023-10-20 22:24 ` [PATCH 6.1.y] net: move altnames together with the netdevice Jakub Kicinski
2023-10-23 7:41 ` 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=2023102304-mortally-safely-9e86@gregkh \
--to=greg@kroah.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.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