From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?K=C3=A9vin_L=27h=C3=B4pital_=3Ckevin=2Elhopital=40savoirfairelinux?=@ci.codeaurora.org,
=?utf-8?q?=2Ecom=3E?=@ci.codeaurora.org
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dmurphy@ti.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
enguerrand.de-ribaucourt@savoirfairelinux.com,
rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH v2] net: phy: fix phy_get_internal_delay accessing an empty array
Date: Fri, 08 Mar 2024 10:20:31 +0000 [thread overview]
Message-ID: <170989323116.6327.2942452458797503240.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240307111906.297749-1-kevin.lhopital@savoirfairelinux.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2024-03-08 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 11:19 [PATCH v2] net: phy: fix phy_get_internal_delay accessing an empty array Kévin L'hôpital
2024-03-08 10:20 ` 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=170989323116.6327.2942452458797503240.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?=2Ecom=3E?=@ci.codeaurora.org \
--cc==?utf-8?q?K=C3=A9vin_L=27h=C3=B4pital_=3Ckevin=2Elhopital=40savoirfairelinux?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=edumazet@google.com \
--cc=enguerrand.de-ribaucourt@savoirfairelinux.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).