From: patchwork-bot+netdevbpf@kernel.org
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: marcin.s.wojtas@gmail.com, linux@armlinux.org.uk,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] net: mvpp2: free pending TX timestamp skbs when the port is stopped
Date: Tue, 10 Nov 2026 18:23:10 +0000 [thread overview]
Message-ID: <179433499017.4118637.2163160814917969670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103100535.1310088-1-vulab@iscas.ac.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Nov 2026 10:05:35 +0000 you wrote:
> mvpp2_tx_hw_tstamp() takes an extra reference on skbs that need a TX
> timestamp and stores them in port->tx_hwtstamp_queue[]. The reference is
> dropped by mvpp2_isr_handle_ptp_queue() when the hardware reports the
> timestamp. Nothing drains the queues when the port is stopped, so skbs
> still waiting for a timestamp keep their reference until their queue
> slot is reused, and are leaked for good when the port is removed.
>
> [...]
Here is the summary with links:
- net: mvpp2: free pending TX timestamp skbs when the port is stopped
https://git.kernel.org/netdev/net-next/c/6c4f0baee69e
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-11-10 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:05 [PATCH] net: mvpp2: free pending TX timestamp skbs when the port is stopped Wentao Liang
2026-11-03 10:10 ` netdev-bot+sinfo
2026-11-08 17:34 ` Simon Horman
2026-11-03 10:25 ` Krzysztof Kozlowski
2026-11-07 12:00 ` netdev-bot+sashiko
2026-11-08 17:28 ` Simon Horman
2026-11-10 18:23 ` 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=179433499017.4118637.2163160814917969670.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcin.s.wojtas@gmail.com \
--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.