From: Jijie Shao <shaojijie@huawei.com>
To: David Yang <mmyangfl@gmail.com>, <netdev@vger.kernel.org>
Cc: shaojijie@huawei.com, "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Ciprian Regus" <ciprian.regus@analog.com>,
"Andreas Larsson" <andreas@gaisler.com>,
"Jian Shen" <shenjian15@huawei.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Parthiban Veerasooran" <parthiban.veerasooran@microchip.com>,
"MD Danish Anwar" <danishanwar@ti.com>,
"Parvathi Pudi" <parvathi@couthit.com>,
"Roger Quadros" <rogerq@kernel.org>,
"Mohan Reddy Putluru" <pmohan@couthit.com>,
"Runyu Xiao" <runyu.xiao@seu.edu.cn>,
"Simon Horman" <horms@kernel.org>,
"Jacob Keller" <jacob.e.keller@intel.com>,
"Stanislav Fomichev" <sdf@fomichev.me>,
"Nicolai Buchwitz" <nb@tipi-net.de>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 00/10] net: Move setting of netops to fix crash
Date: Thu, 8 Oct 2026 20:10:51 +0800 [thread overview]
Message-ID: <66755d59-c6e5-4815-ae67-faf8ec0f6198@huawei.com> (raw)
In-Reply-To: <20261008022656.3592191-1-mmyangfl@gmail.com>
on 2026/10/8 10:26, David Yang wrote:
> Commit ded86da4bbb7 ("net: ethtool: relax ethnl_req_get_phydev()
> locking assertion") put a netdev_need_ops_lock() check on the
> phy_attach_direct() path, in phy_link_topo_add_phy(). With
> CONFIG_NET_SHAPER enabled netdev_need_ops_lock() reads
> dev->netdev_ops->net_shaper_ops, so any driver that connects a PHY
> before assigning ndev->netdev_ops now dies with a NULL pointer
> dereference at probe time. The breakage showed up in v7.3-rc1.
>
> ibm/emac was hit first and fixed by commit 7c9f391ec89c ("net: emac:
> move setting of netops to fix crash"). These ten patches apply the
> same one-line move to the remaining in-tree drivers whose probe path
> attaches a PHY before filling in netdev_ops:
>
> 1. hisilicon/hisi_femac (crash reproduced on hardware)
> 2. hisilicon/hip04
> 3. actions/owl-emac
> 4. adi/adin1140
> 5. marvell/mv643xx_eth
> 6. amd/au1000_eth
> 7. ethoc
> 8. aeroflex/greth
> 9. ti/icssm-prueth
> 10. microchip/lan865x (attach happens inside oa_tc6_init())
>
> Only patch 1 was reproduced and verified on hardware; patches 2-10
> were found by source inspection and are neither build nor boot
> tested.
>
> Note that ti/netcp_ethss and cavium/thunder_bgx attach a PHY to
> netdevs that never get a netdev_ops at all (dummy netdevs), so they
> cannot be fixed by reordering and are not addressed here.
>
> David Yang (10):
> net: hisilicon: hisi_femac: Move setting of netops to fix crash
> net: hisilicon: hip04_eth: Move setting of netops to fix crash
> net: ethernet: actions: Move setting of netops to fix crash
> net: ethernet: adi: Move setting of netops to fix crash
> net: mv643xx: move setting of netops to fix crash
> net: au1000: move setting of netops to fix crash
> net: ethoc: move setting of netops to fix crash
> net: ethernet: aeroflex: move setting of netops to fix crash
> net: ti: icssm-prueth: Move setting of netops to fix crash
> microchip: lan865x: move setting of netops to fix crash
Why isn't the subject of the last patch "net: microchip: lan865x..."
But overall, it's okay.
Reviewed-by: Jijie Shao <shaojijie@huawei.com>
>
> drivers/net/ethernet/actions/owl-emac.c | 3 ++-
> drivers/net/ethernet/adi/adin1140.c | 3 ++-
> drivers/net/ethernet/aeroflex/greth.c | 3 ++-
> drivers/net/ethernet/amd/au1000_eth.c | 3 ++-
> drivers/net/ethernet/ethoc.c | 3 ++-
> drivers/net/ethernet/hisilicon/hip04_eth.c | 3 ++-
> drivers/net/ethernet/hisilicon/hisi_femac.c | 3 ++-
> drivers/net/ethernet/marvell/mv643xx_eth.c | 4 ++--
> drivers/net/ethernet/microchip/lan865x/lan865x.c | 3 ++-
> drivers/net/ethernet/ti/icssm/icssm_prueth.c | 3 ++-
> 10 files changed, 20 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2026-10-08 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 2:26 [PATCH net 00/10] net: Move setting of netops to fix crash David Yang
2026-10-08 2:26 ` [PATCH net 03/10] net: ethernet: actions: " David Yang
2026-10-08 8:30 ` Maxime Chevallier
2026-10-08 2:26 ` [PATCH net 09/10] net: ti: icssm-prueth: " David Yang
2026-10-08 8:32 ` Maxime Chevallier
2026-10-08 12:10 ` Jijie Shao [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=66755d59-c6e5-4815-ae67-faf8ec0f6198@huawei.com \
--to=shaojijie@huawei.com \
--cc=afaerber@suse.de \
--cc=andreas@gaisler.com \
--cc=andrew+netdev@lunn.ch \
--cc=ciprian.regus@analog.com \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mmyangfl@gmail.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parthiban.veerasooran@microchip.com \
--cc=parvathi@couthit.com \
--cc=pmohan@couthit.com \
--cc=rogerq@kernel.org \
--cc=runyu.xiao@seu.edu.cn \
--cc=sdf@fomichev.me \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shenjian15@huawei.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