[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165239881318.13563.9379638810266990590.git-patchwork-notify@kernel.org>
Date: Thu, 12 May 2022 23:40:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
UNGLinuxDriver@...rochip.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
dan.carpenter@...cle.com
Subject: Re: [PATCH net-next] net: lan966x: Fix use of pointer after being freed
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 11 May 2022 22:40:59 +0200 you wrote:
> The smatch found the following warning:
>
> drivers/net/ethernet/microchip/lan966x/lan966x_fdma.c:736 lan966x_fdma_reload()
> warn: 'rx_dcbs' was already freed.
>
> This issue can happen when changing the MTU on one of the ports and once
> the RX buffers are allocated and then the TX buffer allocation fails.
> In that case the RX buffers should not be restore. This fix this issue
> such that the RX buffers will not be restored if the TX buffers failed
> to be allocated.
>
> [...]
Here is the summary with links:
- [net-next] net: lan966x: Fix use of pointer after being freed
https://git.kernel.org/netdev/net-next/c/f0a65f815f64
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