mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Bloch <mbloch@nvidia.com>
Cc: jiri@nvidia.com, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	tariqt@nvidia.com, leon@kernel.org, saeedm@nvidia.com,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, gal@nvidia.com, jiri@resnulli.us
Subject: Re: [PATCH net] devlink: Release nested relation on devlink free
Date: Tue, 02 Jun 2026 03:00:05 +0000	[thread overview]
Message-ID: <178036920566.221457.9205076512445402287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260528191411.3270532-1-mbloch@nvidia.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 28 May 2026 22:14:10 +0300 you wrote:
> devlink relation state is normally released from devl_unregister(), which
> calls devlink_rel_put(). This misses devlink instances that get a nested
> relation before registration and then fail probe before devl_register() is
> reached.
> 
> That flow can happen for SFs. The child devlink gets linked to its
> parent before registration, then a later probe error calls devlink_free()
> directly. Since the instance was never registered, devl_unregister() is not
> called and devlink->rel is leaked.
> 
> [...]

Here is the summary with links:
  - [net] devlink: Release nested relation on devlink free
    https://git.kernel.org/netdev/net/c/3522b21fd7e1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-02  3:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 19:14 Mark Bloch
2026-05-29  9:50 ` Jiri Pirko
2026-06-02  3:00 ` patchwork-bot+netdevbpf [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=178036920566.221457.9205076512445402287.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@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
Powered by JetHome