Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next] net: lan966x: Fix use of pointer after being freed
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <165239881318.13563.9379638810266990590.git-patchwork-notify@kernel.org>
Date:   Thu, 12 May 2022 23:40:13 +0000
References: <20220511204059.2689199-1-horatiu.vultur@microchip.com>
In-Reply-To: <20220511204059.2689199-1-horatiu.vultur@microchip.com>
To:     Horatiu Vultur <horatiu.vultur@microchip.com>
Cc:     netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        UNGLinuxDriver@microchip.com, davem@davemloft.net,
        edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
        dan.carpenter@oracle.com
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.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