All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kuniyuki Iwashima" <kuniyu@google.com>
Cc: linux-can@vger.kernel.org,
	"Oliver Hartkopp" <socketcan@hartkopp.net>,
	"Vincent Mailhol" <mailhol@kernel.org>,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Marc Kleine-Budde" <mkl@pengutronix.de>
Subject: Re: [PATCH RESEND v1] vxcan: Support per-netns device unregistration.
Date: Fri, 31 Jul 2026 23:31:36 +0000	[thread overview]
Message-ID: <20260731233136.A908F1F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260731231755.2474376-1-kuniyu@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch calls a non-existent function `unregister_netdevice_queue_net()`, causing a build failure.
--

--- Patch [1]: [PATCH RESEND v1] vxcan: Support per-netns device unregistration. ---
commit aa743c4ffeab7ce1e07d36aa7e401187541f6f4f
Author: Kuniyuki Iwashima <kuniyu@google.com>

vxcan: Support per-netns device unregistration.

This commit modifies vxcan_dellink() to support concurrent per-netns device
unregistration by using xchg() to ensure each device is queued for
destruction only once. It drops the synchronous RTNL assumption for deleting
both the local and peer devices.

> diff --git a/drivers/net/can/vxcan.c b/drivers/net/can/vxcan.c
> index e882250180ef6..b7efed1226d88 100644
> --- 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)
>  {
[ ... ]
> -	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]
Does unregister_netdevice_queue_net() exist in the source tree? It appears
this will cause a build failure due to an undefined function reference when
the driver is compiled.

> +
> +	netdev_put(peer, peer_tracker);
> +	netdev_put(dev, &priv->peer_tracker);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260731231755.2474376-1-kuniyu@google.com?part=1

  reply	other threads:[~2026-07-31 23:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 23:17 [PATCH RESEND v1] vxcan: Support per-netns device unregistration Kuniyuki Iwashima
2026-07-31 23:31 ` sashiko-bot [this message]
2026-07-31 23:33   ` 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=20260731233136.A908F1F00AC4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.