[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170989323116.6327.2942452458797503240.git-patchwork-notify@kernel.org>
Date: Fri, 08 Mar 2024 10:20:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kévin L'hôpital <kevin.lhopital@...oirfairelinux@...eaurora.org,
.com>@codeaurora.org
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
dmurphy@...com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
enguerrand.de-ribaucourt@...oirfairelinux.com, rmk+kernel@...linux.org.uk
Subject: Re: [PATCH v2] net: phy: fix phy_get_internal_delay accessing an empty
array
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:
On Thu, 7 Mar 2024 12:19:06 +0100 you wrote:
> The phy_get_internal_delay function could try to access to an empty
> array in the case that the driver is calling phy_get_internal_delay
> without defining delay_values and rx-internal-delay-ps or
> tx-internal-delay-ps is defined to 0 in the device-tree.
> This will lead to "unable to handle kernel NULL pointer dereference at
> virtual address 0". To avoid this kernel oops, the test should be delay
> >= 0. As there is already delay < 0 test just before, the test could
> only be size == 0.
>
> [...]
Here is the summary with links:
- [v2] net: phy: fix phy_get_internal_delay accessing an empty array
https://git.kernel.org/netdev/net/c/4469c0c5b14a
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