public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, gregkh@linuxfoundation.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
	jiri@nvidia.com, stable@vger.kernel.org, davem@davemloft.net,
	pabeni@redhat.com, edumazet@google.com, sashal@kernel.org,
	vkarri@nvidia.com
Subject: Re: [PATCH stable 6.1] devlink: Fix RCU stall when unregistering a devlink instance
Date: Sun, 6 Oct 2024 11:44:42 +0300	[thread overview]
Message-ID: <ZwJN-jZ82HpfF9PL@shredder.mtl.com> (raw)
In-Reply-To: <20241001153953.4de43308@kernel.org>

On Tue, Oct 01, 2024 at 03:39:53PM -0700, Jakub Kicinski wrote:
> On Tue, 1 Oct 2024 16:38:39 +0300 Ido Schimmel wrote:
> > > You need to document the heck out of why this is only relevant for this
> > > one specific kernel branch IN the changelog text, so that we understand
> > > what is going on, AND you need to get acks from the relevant maintainers
> > > of this area of the kernel to accept something that is not in Linus's
> > > tree.
> > > 
> > > But first of, why?  Why not just take the upstrema commits instead?  
> > 
> > There were a lot of changes as part of the 6.3 cycle to completely
> > rework the semantics of the devlink instance reference count. As part of
> > these changes, commit d77278196441 ("devlink: bump the instance index
> > directly when iterating") inadvertently fixed the bug mentioned in this
> > patch. This commit cannot be applied to 6.1.y as-is because a prior
> > commit (also in 6.3) moved the code to a different file (leftover.c ->
> > core.c). There might be more dependencies that I'm currently unaware of.
> > 
> > The alternative, proposed in this patch, is to provide a minimal and
> > contained fix for the bug introduced in upstream commit c2368b19807a
> > ("net: devlink: introduce "unregistering" mark and use it during
> > devlinks iteration") as part of the 6.0 cycle.
> > 
> > The above explains why the patch is only relevant to 6.1.y.
> > 
> > Jakub / Jiri, what is your preference here? This patch or cherry picking
> > a lot of code from 6.3?
> 
> No preference here. The fix as posted looks correct. The backport of
> the upstream commit should be correct too (I don't see any
> incompatibilities) but as you said the code has moved and got exposed
> via a header, so the diff will look quite different.
> 
> I think Greg would still prefer to use the bastardized upstream commit
> in such cases.

Greg, if I augment the commit message with the necessary information,
would you be willing to take this patch instead of a much larger patch?

  reply	other threads:[~2024-10-06  8:44 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 [this message]
2024-10-06 10:11         ` Greg KH
2024-10-10 14:08 ` Sasha Levin

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=ZwJN-jZ82HpfF9PL@shredder.mtl.com \
    --to=idosch@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sashal@kernel.org \
    --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