netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jun Gu <jun.gu@easystack.cn>
Cc: pshelar@ovn.org, dev@openvswitch.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eelco Chaudron <echaudro@redhat.com>
Subject: Re: [ovs-dev] [PATCH net-next] net: openvswitch: Release reference to netdev
Date: Tue, 23 Apr 2024 12:15:18 +0100	[thread overview]
Message-ID: <20240423111518.GQ42092@kernel.org> (raw)
In-Reply-To: <20240423073751.52706-1-jun.gu@easystack.cn>

+ David Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni, Eelco Chaudron

On Tue, Apr 23, 2024 at 03:37:51PM +0800, Jun Gu wrote:
> dev_get_by_name will provide a reference on the netdev. So ensure that
> the reference of netdev is released after completed.
> 
> Fixes: 2540088b836f ("net: openvswitch: Check vport netdev name")
> Signed-off-by: Jun Gu <jun.gu@easystack.cn>

Hi Jun Gu,

This change looks good to me.

Unfortunately  didn't seem to hit netdev for some reason.

And, probably unrelated to that some CCs were missing:
they should be seeded using ./scripts/get_maintainer.pl my.patch

I'd wait for feedback from Jakub on if a repost is needed
(because for one thing it's not good to repost within 24h.)

The above notwithstanding,

Reviewed-by: Simon Horman <horms@kernel.org>

> ---
>  net/openvswitch/vport-netdev.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/net/openvswitch/vport-netdev.c b/net/openvswitch/vport-netdev.c
> index 618edc346c0f..91a11067e458 100644
> --- a/net/openvswitch/vport-netdev.c
> +++ b/net/openvswitch/vport-netdev.c
> @@ -78,12 +78,16 @@ struct vport *ovs_netdev_link(struct vport *vport, const char *name)
>  	int err;
>  
>  	vport->dev = dev_get_by_name(ovs_dp_get_net(vport->dp), name);
> +	if (!vport->dev) {
> +		err = -ENODEV;
> +		goto error_free_vport;
> +	}
>  	/* Ensure that the device exists and that the provided
>  	 * name is not one of its aliases.
>  	 */
> -	if (!vport->dev || strcmp(name, ovs_vport_name(vport))) {
> +	if (strcmp(name, ovs_vport_name(vport))) {
>  		err = -ENODEV;
> -		goto error_free_vport;
> +		goto error_put;
>  	}
>  	netdev_tracker_alloc(vport->dev, &vport->dev_tracker, GFP_KERNEL);
>  	if (vport->dev->flags & IFF_LOOPBACK ||
> -- 
> 2.25.1
> 
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
> 

  reply	other threads:[~2024-04-23 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  7:37 [PATCH net-next] net: openvswitch: Release reference to netdev Jun Gu
2024-04-23 11:15 ` Simon Horman [this message]
2024-04-23 11:19 ` [ovs-dev] " Eelco Chaudron
2024-04-24 15:05 ` Aaron Conole
2024-04-25  0:10 ` 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=20240423111518.GQ42092@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=jun.gu@easystack.cn \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.org \
    /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;
as well as URLs for NNTP newsgroup(s).