From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] net: dsa: sja1105: protect link replay helpers against NULL phylink instance
Date: Wed, 18 Feb 2026 18:10:37 +0200 [thread overview]
Message-ID: <20260218161037.a4uyxtku2hbsnfzx@skbuf> (raw)
In-Reply-To: <aZXj8QbM5-0tpl4s@shell.armlinux.org.uk> <aZXj8QbM5-0tpl4s@shell.armlinux.org.uk>
On Wed, Feb 18, 2026 at 04:08:17PM +0000, Russell King (Oracle) wrote:
> On Wed, Feb 18, 2026 at 06:05:51PM +0200, Vladimir Oltean wrote:
> > There are multiple levels at which this could be avoided:
> > - add an "if (dp->pl)" in sja1105_static_config_reload()
> > - make the phylink replay helpers NULL-tolerant
> > - mark ports as DSA_PORT_TYPE_UNUSED after dsa_port_phylink_destroy()
> > has run, such that subsequent dsa_switch_for_each_available_port()
> > iterations skip them
> > - disconnect the entire switch at once from switchdev and
> > NETDEV_CHANGEUPPER events while unbinding, not just port by port,
> > likely using a "ds->unbinding = true" mechanism or similar
> >
> > however options 3 and 4 are quite heavy and might have side effects.
> > Although 2 allows to keep the driver simpler, the phylink API it not
> > NULL-tolerant in general and is not responsible for the NULL pointer
> > (this is something done by dsa_port_phylink_destroy()). So I went
> > with 1.
>
> ^^^^^^^^
>
> > v1->v2: select option 1 instead of 2
>
> Given this, I think the paragraph above needs updating.
Sorry, I don't understand what needs updating.
next prev parent reply other threads:[~2026-02-18 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 16:05 [PATCH v2 net] net: dsa: sja1105: protect link replay helpers against NULL phylink instance Vladimir Oltean
2026-02-18 16:08 ` Russell King (Oracle)
2026-02-18 16:10 ` Vladimir Oltean [this message]
2026-02-18 16:21 ` Russell King (Oracle)
2026-02-18 16:39 ` Vladimir Oltean
2026-02-18 16:53 ` Andrew Lunn
2026-02-19 23:00 ` patchwork-bot+netdevbpf
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=20260218161037.a4uyxtku2hbsnfzx@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=pabeni@redhat.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