From: patchwork-bot+netdevbpf@kernel.org
To: Prashant Sengar <prashantsengar25031@gmail.com>
Cc: netdev@vger.kernel.org, Thangaraj.S@microchip.com,
UNGLinuxDriver@microchip.com, andrew+netdev@lunn.ch,
linux-usb@vger.kernel.org
Subject: Re: [PATCH net v4] net: usb: lan78xx: avoid NULL PHY dereference in WoL setup
Date: Mon, 26 Oct 2026 23:20:05 +0000 [thread overview]
Message-ID: <179305680557.3450824.4724998894519023097.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020201537.2465655-1-prashantsengar25031@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Oct 2026 01:45:37 +0530 you wrote:
> LAN7801 supports fixed-link configurations without an attached PHY.
> However, lan78xx_set_wol() unconditionally passes netdev->phydev
> to phy_ethtool_set_wol(), causing a NULL pointer dereference when
> a userspace WoL request reaches this path.
>
> Report no WoL capabilities when no PHY is attached, and return
> -EOPNOTSUPP from lan78xx_set_wol() before modifying the wakeup
> configuration. Keep the existing phylib WoL handling for devices
> with an attached PHY.
>
> [...]
Here is the summary with links:
- [net,v4] net: usb: lan78xx: avoid NULL PHY dereference in WoL setup
https://git.kernel.org/netdev/net/c/dacb77e32e2b
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:[~2026-10-26 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 20:15 [PATCH net v4] net: usb: lan78xx: avoid NULL PHY dereference in WoL setup Prashant Sengar
2026-10-22 20:16 ` netdev-bot+sashiko
2026-10-24 1:02 ` Prashant Sengar
[not found] ` <20261020201716.94FAA1F000C9@smtp.kernel.org>
[not found] ` <20261020152211.73eb8f98@kernel.org>
2026-10-24 1:17 ` Prashant Sengar
2026-10-26 23: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=179305680557.3450824.4724998894519023097.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=prashantsengar25031@gmail.com \
/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