From: patchwork-bot+netdevbpf@kernel.org
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Rengarajan.S@microchip.com, Thangaraj.S@microchip.com,
UNGLinuxDriver@microchip.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com,
john.efstathiades@pebblebay.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
stable@vger.kernel.org
Subject: Re: [PATCH] net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs()
Date: Tue, 22 Sep 2026 14:00:04 +0000 [thread overview]
Message-ID: <179008560489.4097520.9027717710600492085.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260917115811.2150119-1-vulab@iscas.ac.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 17 Sep 2026 11:58:11 +0000 you wrote:
> usb_get_from_anchor() hands over a reference to the URB, which the caller
> must release. lan78xx_submit_deferred_urbs() never does, so every deferred
> Tx URB keeps an extra reference: the counter grows on each suspend/resume
> cycle and the URBs are never freed when the buffers are released. Drop
> the reference after submitting, and on the path that drops the packet
> instead of submitting it.
>
> [...]
Here is the summary with links:
- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs()
https://git.kernel.org/netdev/net/c/17741334d00b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-22 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:58 [PATCH] net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() Wentao Liang
2026-09-22 14: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=179008560489.4097520.9027717710600492085.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.efstathiades@pebblebay.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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.