From: sashiko-bot@kernel.org
To: "Kuniyuki Iwashima" <kuniyu@google.com>
Cc: "Oliver Hartkopp" <socketcan@hartkopp.net>,
linux-can@vger.kernel.org,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Vincent Mailhol" <mailhol@kernel.org>
Subject: Re: [PATCH v1] vxcan: Support per-netns device unregistration.
Date: Sun, 12 Jul 2026 21:34:22 +0000 [thread overview]
Message-ID: <20260712213422.DB1111F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260712212113.181121-1-kuniyu@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch calls the undefined function `unregister_netdevice_queue_net()`, resulting in a compilation error.
--
--- Patch [1]: [PATCH v1] vxcan: Support per-netns device unregistration. ---
commit 882fcd31630d9ce6b0a57cc99738c2ad0579763f
Author: Kuniyuki Iwashima <kuniyu@google.com>
vxcan: Support per-netns device unregistration.
This commit updates vxcan_dellink() to unregister local and peer devices
safely across different namespaces by using xchg(). The change aims to
prevent double-queuing of device destruction when RTNL is removed.
> diff --git a/drivers/net/can/vxcan.c b/drivers/net/can/vxcan.c
> --- a/drivers/net/can/vxcan.c
> +++ b/drivers/net/can/vxcan.c
[ ... ]
> @@ -281,24 +284,25 @@ static int vxcan_newlink(struct net_device *dev,
>
> static void vxcan_dellink(struct net_device *dev, struct list_head *head)
> {
[ ... ]
> unregister_netdevice_queue(dev, head);
>
> - if (peer) {
> - priv = netdev_priv(peer);
> - RCU_INIT_POINTER(priv->peer, NULL);
> - unregister_netdevice_queue(peer, head);
> - }
> + priv = netdev_priv(peer);
> + dev = unrcu_pointer(xchg(&priv->peer, NULL));
> + if (dev)
> + unregister_netdevice_queue_net(dev_net(dev), peer, head);
[Severity: Low]
Is this missing a prerequisite patch? It appears that
unregister_netdevice_queue_net() is not defined anywhere in the kernel
tree, which leads to a compilation error when building vxcan.c.
> +
> + netdev_put(peer, peer_tracker);
> + netdev_put(dev, &priv->peer_tracker);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260712212113.181121-1-kuniyu@google.com?part=1
next prev parent reply other threads:[~2026-07-12 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 21:21 [PATCH v1] vxcan: Support per-netns device unregistration Kuniyuki Iwashima
2026-07-12 21:34 ` sashiko-bot [this message]
2026-07-13 7:56 ` Oliver Hartkopp
2026-07-14 9:30 ` Kuniyuki Iwashima
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=20260712213422.DB1111F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=sashiko-reviews@lists.linux.dev \
--cc=socketcan@hartkopp.net \
/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