Devicetree
 help / color / mirror / Atom feed
From: "Alvin Šipraga" <alvin.sipraga@analog.com>
To: sashiko-reviews@lists.linux.dev
Cc: Iustin Stolniceanu <iustin.stolniceanu@analog.com>,
	devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v2 7/7] net: ethernet: adi: adin1110: Add OA TC6 protocol support for ADIN1110
Date: Tue, 10 Nov 2026 10:54:06 +0100	[thread overview]
Message-ID: <avLpeyOXz5yqBuFI@analog.com> (raw)
In-Reply-To: <sashiko-outbox-206699@kernel.org>

On Tue, Nov 10, 2026 at 09:02:26AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue to consider:
> - [High] net: adin1110: NULL netdev_ops dereference in
>   adin1110_oa_tc6_probe()
> --
> 
> commit a8946759404622a473f14b5de5bca9f8c82eea9c
> Author: Ciprian Regus <ciprian.regus@analog.com>
> 
> net: ethernet: adi: adin1110: Add OA TC6 protocol support for ADIN1110
> 
> This commit adds OPEN Alliance TC6 SPI protocol support for the ADIN1110
> using the oa_tc6 framework when the adi,spi-oa-tc6 property is present.
> 

[...]

> > +
> > +	netdev->if_port = IF_PORT_10BASET;
> > +	netdev->netdev_ops = &adin1110_tc6_netdev_ops;
> 
> [Severity: High]
> Does calling oa_tc6_init() before setting netdev->netdev_ops cause a NULL
> pointer dereference when CONFIG_NET_SHAPER is enabled?
> 
> oa_tc6_init() calls oa_tc6_phy_init() -> phy_connect_direct() ->
> phy_attach_direct() -> phy_link_topo_add_phy() -> netdev_need_ops_lock(),
> which dereferences dev->netdev_ops->net_shaper_ops while netdev->netdev_ops
> is still NULL.

If this report is legit, then it looks like adin1140.c has the same
problem. Just FYI.

> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20261109085952.105331-1-iustin.stolniceanu@analog.com?part=7

      reply	other threads:[~2026-11-10  9:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  8:59 [PATCH net-next v2 0/7] net: ethernet: adi: adin1110: Add OPEN Alliance TC6 support Iustin Stolniceanu
2026-11-09  8:59 ` [PATCH net-next v2 1/7] net: ethernet: oa_tc6: Forward declare struct mii_bus Iustin Stolniceanu
2026-11-10  9:42   ` Alvin Šipraga
2026-11-09  8:59 ` [PATCH net-next v2 2/7] net: ethernet: oa_tc6: Allow custom reset settle time values Iustin Stolniceanu
2026-11-09 17:10   ` Selvamani Rajagopal
2026-11-09  8:59 ` [PATCH net-next v2 3/7] net: ethernet: oa_tc6: Add support for MDIO indirect access Iustin Stolniceanu
2026-11-09  8:59 ` [PATCH net-next v2 4/7] net: phy: adin1100: Add separate driver entries for ADIN1110/ADIN2111 Iustin Stolniceanu
2026-11-10  9:46   ` Alvin Šipraga
2026-11-09  8:59 ` [PATCH net-next v2 5/7] net: phy: adin1100: Skip the soft reset on ADIN1110/ADIN2111 Iustin Stolniceanu
2026-11-10  9:48   ` Alvin Šipraga
2026-11-09  8:59 ` [PATCH net-next v2 6/7] dt-bindings: net: adi,adin1110: Add adi,spi-oa-tc6 Iustin Stolniceanu
2026-11-10  8:05   ` Krzysztof Kozlowski
2026-11-09  8:59 ` [PATCH net-next v2 7/7] net: ethernet: adi: adin1110: Add OA TC6 protocol support for ADIN1110 Iustin Stolniceanu
2026-11-10  9:02   ` sashiko-bot
2026-11-10  9:54     ` Alvin Šipraga [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=avLpeyOXz5yqBuFI@analog.com \
    --to=alvin.sipraga@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iustin.stolniceanu@analog.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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