mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: mctp: Ensure keys maintain only one ref to corresponding dev
Date: Fri, 09 May 2025 23:30:33 +0000	[thread overview]
Message-ID: <174683343349.3841790.11374991133112180926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250508-mctp-dev-refcount-v1-1-d4f965c67bb5@codeconstruct.com.au>

Hello:

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

On Thu, 08 May 2025 14:16:00 +0930 you wrote:
> mctp_flow_prepare_output() is called in mctp_route_output(), which
> places outbound packets onto a given interface. The packet may represent
> a message fragment, in which case we provoke an unbalanced reference
> count to the underlying device. This causes trouble if we ever attempt
> to remove the interface:
> 
>     [   48.702195] usb 1-1: USB disconnect, device number 2
>     [   58.883056] unregister_netdevice: waiting for mctpusb0 to become free. Usage count = 2
>     [   69.022548] unregister_netdevice: waiting for mctpusb0 to become free. Usage count = 2
>     [   79.172568] unregister_netdevice: waiting for mctpusb0 to become free. Usage count = 2
>     ...
> 
> [...]

Here is the summary with links:
  - [net] net: mctp: Ensure keys maintain only one ref to corresponding dev
    https://git.kernel.org/netdev/net/c/e4f349bd6e58

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



      reply	other threads:[~2025-05-09 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  4:46 Andrew Jeffery
2025-05-09 23:30 ` 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=174683343349.3841790.11374991133112180926.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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
all inboxes | Powered by JetHome®