From: patchwork-bot+netdevbpf@kernel.org
To: Andre Kalb <svc.sw.rte.linux@sma.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, felix.riemann@sma.de
Subject: Re: [PATCH net] net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices
Date: Sat, 28 Jan 2023 08:40:17 +0000 [thread overview]
Message-ID: <167489521762.20245.17614376915364522830.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y9FzniUhUtbaGKU7@pc6682>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 25 Jan 2023 19:23:26 +0100 you wrote:
> From: Andre Kalb <andre.kalb@sma.de>
>
> The probe() function is only used for the DP83822 PHY, leaving the
> private data pointer uninitialized for the smaller DP83825/26 models.
> While all uses of the private data structure are hidden in 82822 specific
> callbacks, configuring the interrupt is shared across all models.
> This causes a NULL pointer dereference on the smaller PHYs as it accesses
> the private data unchecked. Verifying the pointer avoids that.
>
> [...]
Here is the summary with links:
- [net] net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices
https://git.kernel.org/netdev/net/c/422ae7d9c722
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:[~2023-01-28 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:23 [PATCH net] net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices Andre Kalb
2023-01-26 7:21 ` Simon Horman
2023-01-28 8:40 ` 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=167489521762.20245.17614376915364522830.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=felix.riemann@sma.de \
--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=svc.sw.rte.linux@sma.de \
/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).