All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
	olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] net: dsa: don't leak tagger-owned storage on switch driver unbind
Date: Wed, 16 Nov 2022 05:10:15 +0000	[thread overview]
Message-ID: <166857541586.12533.2602592342499682605.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114143551.1906361-1-vladimir.oltean@nxp.com>

Hello:

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

On Mon, 14 Nov 2022 16:35:51 +0200 you wrote:
> In the initial commit dc452a471dba ("net: dsa: introduce tagger-owned
> storage for private and shared data"), we had a call to
> tag_ops->disconnect(dst) issued from dsa_tree_free(), which is called at
> tree teardown time.
> 
> There were problems with connecting to a switch tree as a whole, so this
> got reworked to connecting to individual switches within the tree. In
> this process, tag_ops->disconnect(ds) was made to be called only from
> switch.c (cross-chip notifiers emitted as a result of dynamic tag proto
> changes), but the normal driver teardown code path wasn't replaced with
> anything.
> 
> [...]

Here is the summary with links:
  - [net] net: dsa: don't leak tagger-owned storage on switch driver unbind
    https://git.kernel.org/netdev/net/c/4e0c19fcb8b5

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



      parent reply	other threads:[~2022-11-16  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 14:35 [PATCH net] net: dsa: don't leak tagger-owned storage on switch driver unbind Vladimir Oltean
2022-11-15 21:57 ` Saeed Mahameed
2022-11-15 22:52 ` Florian Fainelli
2022-11-16  5:10 ` 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=166857541586.12533.2602592342499682605.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.