From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"olteanv@gmail.com" <olteanv@gmail.com>,
"daniel.klauer@gin.de" <daniel.klauer@gin.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
"LinoSanfilippo@gmx.de" <LinoSanfilippo@gmx.de>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"rafael.richter@gin.de" <rafael.richter@gin.de>
Subject: Re: [PATCH net] net: dsa: fix panic when DSA master device unbinds on shutdown
Date: Mon, 9 Sep 2024 17:16:25 +0300 [thread overview]
Message-ID: <20240909120507.vuavas2oqr2237rp@skbuf> (raw)
In-Reply-To: <7db5996ef488f8ca1b9fdc0d39b9e4dd1189b34b.camel@siemens.com>
On Thu, Sep 05, 2024 at 07:11:44AM +0000, Sverdlin, Alexander wrote:
> Hello Vladimir,
>
> On Wed, 2024-09-04 at 10:03 +0200, Alexander Sverdlin wrote:
> > > + /* Disconnect from further netdevice notifiers on the master,
> > > + * since netdev_uses_dsa() will now return false.
> > > + */
> > > + dsa_switch_for_each_cpu_port(dp, ds)
> > > + dp->master->dsa_ptr = NULL;
> >
> > This is unfortunately racy and leads to other panics:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
> > CPU: 0 PID: 12 Comm: ksoftirqd/0 Tainted: G O 6.1.99+gitb7793b7d9b35 #1
> > pc : lan9303_rcv+0x64/0x210
> > lr : lan9303_rcv+0x148/0x210
> > Call trace:
> > lan9303_rcv+0x64/0x210
> > dsa_switch_rcv+0x1d8/0x350
> > __netif_receive_skb_list_core+0x1f8/0x220
> > netif_receive_skb_list_internal+0x18c/0x2a4
> > napi_gro_receive+0x238/0x254
> > fec_enet_rx_napi+0x830/0xe60
> > __napi_poll+0x40/0x210
> > net_rx_action+0x138/0x2d0
> >
> > Even though dsa_switch_rcv() checks
> >
> > if (unlikely(!cpu_dp)) {
> > kfree_skb(skb);
> > return 0;
> > }
> >
> > if dsa_switch_shutdown() happens to zero dsa_ptr before
> > dsa_conduit_find_user(dev, 0, port) call, the latter will dereference dsa_ptr==NULL:
> >
> > static inline struct net_device *dsa_conduit_find_user(struct net_device *dev,
> > int device, int port)
> > {
> > struct dsa_port *cpu_dp = dev->dsa_ptr;
> > struct dsa_switch_tree *dst = cpu_dp->dst;
> >
> > I believe there are other race patterns as well if we consider all possible
> >
> > static int dsa_switch_rcv(struct sk_buff *skb, struct net_device *dev,
> > struct packet_type *pt, struct net_device *unused)
> > {
> > struct metadata_dst *md_dst = skb_metadata_dst(skb);
> > struct dsa_port *cpu_dp = dev->dsa_ptr;
> >
> > ...
> >
> > nskb = cpu_dp->rcv(skb, dev);
> >
> > >
> > > rtnl_unlock();
> > > mutex_unlock(&dsa2_mutex);
> >
> > I'm not sure there is a safe way to zero dsa_ptr without ensuring the port
> > is down and there is no ongoing receive in parallel.
>
> after my first attempts to put a band aid on this failed, I concluded
> that both assignments "dsa_ptr = NULL;" in kernel are broken. Or, being more
> precise, they break widely spread pattern
>
> CPU0 CPU1
> if (netdev_uses_dsa())
> dev->dsa_ptr = NULL;
> dev->dsa_ptr->...
>
> because there is no synchronization whatsoever, so tearing down DSA is actually
> broken in many places...
>
> Seems that something lock-free is required for dsa_ptr, maybe RCU or refcounting,
> I'll try to come up with some rework, but any hints are welcome!
I'm trying to understand if this rework still leads to NULL dereferences
of conduit->dsa_ptr in the receive path? Could you please test?
diff --git a/net/dsa/dsa.c b/net/dsa/dsa.c
index 668c729946ea..f1ce6d8dc499 100644
--- a/net/dsa/dsa.c
+++ b/net/dsa/dsa.c
@@ -1576,32 +1576,7 @@ EXPORT_SYMBOL_GPL(dsa_unregister_switch);
*/
void dsa_switch_shutdown(struct dsa_switch *ds)
{
- struct net_device *conduit, *user_dev;
- struct dsa_port *dp;
-
- mutex_lock(&dsa2_mutex);
-
- if (!ds->setup)
- goto out;
-
- rtnl_lock();
-
- dsa_switch_for_each_user_port(dp, ds) {
- conduit = dsa_port_to_conduit(dp);
- user_dev = dp->user;
-
- netdev_upper_dev_unlink(conduit, user_dev);
- }
-
- /* Disconnect from further netdevice notifiers on the conduit,
- * since netdev_uses_dsa() will now return false.
- */
- dsa_switch_for_each_cpu_port(dp, ds)
- dp->conduit->dsa_ptr = NULL;
-
- rtnl_unlock();
-out:
- mutex_unlock(&dsa2_mutex);
+ dsa_unregister_switch(ds);
}
EXPORT_SYMBOL_GPL(dsa_switch_shutdown);
next prev parent reply other threads:[~2024-09-09 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 12:04 [PATCH net] net: dsa: fix panic when DSA master device unbinds on shutdown Vladimir Oltean
2022-02-09 13:30 ` patchwork-bot+netdevbpf
2024-04-10 9:03 ` Some questions " xu
2024-04-10 9:06 ` xu
2024-04-10 9:14 ` Paolo Abeni
2024-04-10 14:34 ` Vladimir Oltean
2024-04-10 14:55 ` Greg KH
2024-04-10 16:30 ` Sasha Levin
2024-09-04 8:03 ` Sverdlin, Alexander
2024-09-05 7:11 ` Sverdlin, Alexander
2024-09-09 14:16 ` Vladimir Oltean [this message]
2024-09-09 14:23 ` Sverdlin, Alexander
2024-09-10 4:49 ` Sverdlin, Alexander
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=20240909120507.vuavas2oqr2237rp@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=LinoSanfilippo@gmx.de \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=daniel.klauer@gin.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rafael.richter@gin.de \
--cc=vivien.didelot@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