From: Sasha Levin <sashal@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: stable@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, jiri@nvidia.com,
gregkh@linuxfoundation.org, vkarri@nvidia.com
Subject: Re: [PATCH stable 6.1] devlink: Fix RCU stall when unregistering a devlink instance
Date: Thu, 10 Oct 2024 10:08:32 -0400 [thread overview]
Message-ID: <Zwff4AQe7irl4KZu@sashalap> (raw)
In-Reply-To: <20241001112035.973187-1-idosch@nvidia.com>
On Tue, Oct 01, 2024 at 02:20:35PM +0300, Ido Schimmel wrote:
>I read the stable rules and I am not providing an "upstream commit ID"
>since the code in upstream has been reworked, making this fix
>irrelevant. The only affected stable kernel is 6.1.y.
Could you please add some information about *how* the code has changed
so backporting became infeasible? In our experience, custom backports
tend to cause more pain than what they fix, so at least our
future-selves could use some pointers around what happened here.
--
Thanks,
Sasha
prev parent reply other threads:[~2024-10-10 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:20 [PATCH stable 6.1] devlink: Fix RCU stall when unregistering a devlink instance Ido Schimmel
2024-10-01 12:11 ` Greg KH
2024-10-01 13:38 ` Ido Schimmel
2024-10-01 16:47 ` Aleksandr Nogikh
2024-10-06 8:51 ` Ido Schimmel
2024-10-01 22:39 ` Jakub Kicinski
2024-10-06 8:44 ` Ido Schimmel
2024-10-06 10:11 ` Greg KH
2024-10-10 14:08 ` Sasha Levin [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=Zwff4AQe7irl4KZu@sashalap \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vkarri@nvidia.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