[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174839943674.1866481.1704860946542275477.git-patchwork-notify@kernel.org>
Date: Wed, 28 May 2025 02:30:36 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
richardcochran@...il.com, kory.maincent@...tlin.com, shannon.nelson@....com,
rrameshbabu@...dia.com, viro@...iv.linux.org.uk, quentin.schulz@...tlin.com,
atenart@...nel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net v2] net: phy: mscc: Fix memory leak when using one step
timestamping
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 22 May 2025 13:57:22 +0200 you wrote:
> Fix memory leak when running one-step timestamping. When running
> one-step sync timestamping, the HW is configured to insert the TX time
> into the frame, so there is no reason to keep the skb anymore. As in
> this case the HW will never generate an interrupt to say that the frame
> was timestamped, then the frame will never released.
> Fix this by freeing the frame in case of one-step timestamping.
>
> [...]
Here is the summary with links:
- [net,v2] net: phy: mscc: Fix memory leak when using one step timestamping
https://git.kernel.org/netdev/net/c/846992645b25
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists