From: patchwork-bot+netdevbpf@kernel.org
To: Jijie Shao <shaojijie@huawei.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, shenjian15@huawei.com,
liuyonglong@huawei.com, chenhao418@huawei.com,
yangshuaisong@h-partners.com, ningwei15@huawei.com,
shiyongbang@huawei.com, fengzheng6@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: hibmcge: set netdev_ops before hbg_init() to fix NULL pointer dereference
Date: Thu, 22 Oct 2026 00:30:16 +0000 [thread overview]
Message-ID: <179262901677.1378903.766655502279729876.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016110421.2288670-1-shaojijie@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Oct 2026 19:04:21 +0800 you wrote:
> The driver assigns netdev_ops after hbg_init(), but hbg_init() calls
> hbg_mdio_init() -> hbg_phy_connect() -> phy_connect_direct() ->
> phy_attach_direct() -> phy_link_topo_add_phy(), which invokes
> netdev_need_ops_lock(). With CONFIG_NET_SHAPER enabled, this function
> dereferences dev->netdev_ops->net_shaper_ops. Since netdev_ops is still
> NULL at this point, a NULL pointer dereference occurs.
>
> [...]
Here is the summary with links:
- [net] net: hibmcge: set netdev_ops before hbg_init() to fix NULL pointer dereference
https://git.kernel.org/netdev/net/c/9b8ae9aaa1b8
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-22 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 11:04 Jijie Shao
2026-10-16 11:09 ` netdev-bot+sinfo
2026-10-16 11:55 ` Jijie Shao
2026-10-16 12:26 ` Daniel Machon
2026-10-22 0:30 ` 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=179262901677.1378903.766655502279729876.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fengzheng6@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=ningwei15@huawei.com \
--cc=pabeni@redhat.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=shiyongbang@huawei.com \
--cc=yangshuaisong@h-partners.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
all inboxes | Powered by JetHome®