netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Florent Fourcot <florent.fourcot@wifirst.fr>
Cc: netdev@vger.kernel.org, cong.wang@bytedance.com,
	edumazet@google.com, Brian Baboch <brian.baboch@wifirst.fr>
Subject: Re: [PATCH v3 net-next 3/4] rtnetlink: return ENODEV when ifname does not exist and group is given
Date: Tue, 5 Apr 2022 17:47:43 -0700	[thread overview]
Message-ID: <20220405174743.153b1a36@kernel.org> (raw)
In-Reply-To: <20220405134237.16533-3-florent.fourcot@wifirst.fr>

On Tue,  5 Apr 2022 15:42:36 +0200 Florent Fourcot wrote:
> Changes in v3:
>   * Use a boolean to have condition duplication
> 
> Signed-off-by: Florent Fourcot <florent.fourcot@wifirst.fr>
> Signed-off-by: Brian Baboch <brian.baboch@wifirst.fr>
> ---
>  net/core/rtnetlink.c | 18 ++++++++++++++----
>  1 file changed, 14 insertions(+), 4 deletions(-)
> 
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index 33dbeed7e531..e93f4058cf08 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -3279,6 +3279,7 @@ static int __rtnl_newlink(struct sk_buff *skb, struct nlmsghdr *nlh,
>  	struct net *dest_net, *link_net;
>  	struct nlattr **slave_data;
>  	char kind[MODULE_NAME_LEN];
> +	bool link_lookup = false;

link_specified ? Somehow link_lookup does not speak to me.

>  	struct net_device *dev;
>  	struct ifinfomsg *ifm;
>  	char ifname[IFNAMSIZ];
> @@ -3298,12 +3299,15 @@ static int __rtnl_newlink(struct sk_buff *skb, struct nlmsghdr *nlh,
>  		return err;
>  
>  	ifm = nlmsg_data(nlh);
> -	if (ifm->ifi_index > 0)
> +	if (ifm->ifi_index > 0) {
> +		link_lookup = true;
>  		dev = __dev_get_by_index(net, ifm->ifi_index);
> -	else if (tb[IFLA_IFNAME] || tb[IFLA_ALT_IFNAME])
> +	} else if (tb[IFLA_IFNAME] || tb[IFLA_ALT_IFNAME]) {
> +		link_lookup = true;
>  		dev = rtnl_dev_get(net, tb);
> -	else
> +	} else {
>  		dev = NULL;

maybe set it to false here and don't do the initialization.
It doesn't matter in practice but the function has a "retry"
goto which skips the init.

> +	}
>  
>  	master_dev = NULL;
>  	m_ops = NULL;
> @@ -3405,8 +3409,14 @@ static int __rtnl_newlink(struct sk_buff *skb, struct nlmsghdr *nlh,
>  		return do_setlink(skb, dev, ifm, extack, tb, status);
>  	}
>  
> +

spurious new line

>  	if (!(nlh->nlmsg_flags & NLM_F_CREATE)) {
> -		if (ifm->ifi_index == 0 && tb[IFLA_GROUP])
> +		/* No dev found and NLM_F_CREATE not set. Requested dev does not exist,
> +		 * or it's for a group
> +		*/
> +		if (link_lookup)
> +			return -ENODEV;
> +		if (tb[IFLA_GROUP])

  reply	other threads:[~2022-04-06  6:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 13:42 [PATCH v3 net-next 1/4] rtnetlink: enable alt_ifname for setlink/newlink Florent Fourcot
2022-04-05 13:42 ` [PATCH v3 net-next 2/4] rtnetlink: return ENODEV when IFLA_ALT_IFNAME is used in dellink Florent Fourcot
2022-04-05 13:42 ` [PATCH v3 net-next 3/4] rtnetlink: return ENODEV when ifname does not exist and group is given Florent Fourcot
2022-04-06  0:47   ` Jakub Kicinski [this message]
2022-04-05 13:42 ` [PATCH v3 net-next 4/4] rtnetlink: return EINVAL when request cannot succeed Florent Fourcot
2022-04-22  3:50   ` Saeed Mahameed
2022-04-22  4:16     ` Eric Dumazet
2022-04-06  0:41 ` [PATCH v3 net-next 1/4] rtnetlink: enable alt_ifname for setlink/newlink Jakub Kicinski
2022-04-07 12:34   ` Florent Fourcot
2022-04-07 16:11     ` Jakub Kicinski
  -- strict thread matches above, loose matches on Subject: below --
2022-04-07 12:25 [PATCH v3 net-next 0/4] rtnetlink: improve ALT_IFNAME config and fix dangerous GROUP usage Florent Fourcot
2022-04-07 12:25 ` [PATCH v3 net-next 3/4] rtnetlink: return ENODEV when ifname does not exist and group is given Florent Fourcot

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=20220405174743.153b1a36@kernel.org \
    --to=kuba@kernel.org \
    --cc=brian.baboch@wifirst.fr \
    --cc=cong.wang@bytedance.com \
    --cc=edumazet@google.com \
    --cc=florent.fourcot@wifirst.fr \
    --cc=netdev@vger.kernel.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).