From: patchwork-bot+netdevbpf@kernel.org
To: Yi Cong <cong.yi@linux.dev>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jackychou@asix.com.tw,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
yicong@kylinos.cn, stable@vger.kernel.org
Subject: Re: [PATCH net-next] net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup()
Date: Tue, 04 Aug 2026 01:00:06 +0000 [thread overview]
Message-ID: <178580520614.2899965.8757939088248761753.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260729030436.3420477-1-cong.yi@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Jul 2026 11:04:36 +0800 you wrote:
> From: Yi Cong <yicong@kylinos.cn>
>
> When the interface has NETIF_F_SG enabled and skb_linearize() fails in
> ax88179_tx_fixup(), the function returns NULL without freeing the skb.
>
> usbnet_start_xmit() treats a NULL return from tx_fixup() as a drop
> (info->flags does not set FLAG_MULTI_PACKET for this driver), jumping
> to the "drop" label where it does `if (skb) dev_kfree_skb_any(skb)`.
> Because tx_fixup() returned NULL, the local skb variable in
> usbnet_start_xmit() is NULL, so the original skb is never freed — a
> memory leak on every TX frame whose linearization fails (i.e. under
> memory pressure).
>
> [...]
Here is the summary with links:
- [net-next] net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup()
https://git.kernel.org/netdev/net/c/1f428e309473
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-08-04 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 3:04 [PATCH net-next] net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() Yi Cong
2026-08-04 1: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=178580520614.2899965.8757939088248761753.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cong.yi@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jackychou@asix.com.tw \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yicong@kylinos.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.