All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <horms@kernel.org>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
	<edumazet@google.com>, <kuba@kernel.org>, <kuni1840@gmail.com>,
	<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>
Subject: Re: [PATCH v2 net-next 10/14] ipv6: Factorise ip6_route_multipath_add().
Date: Fri, 11 Apr 2025 12:33:46 -0700	[thread overview]
Message-ID: <20250411193347.47836-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250411103404.GY395307@horms.kernel.org>

From: Simon Horman <horms@kernel.org>
Date: Fri, 11 Apr 2025 11:34:04 +0100
> > +static int ip6_route_mpath_info_create_nh(struct list_head *rt6_nh_list,
> > +					  struct netlink_ext_ack *extack)
> > +{
> > +	struct rt6_nh *nh, *nh_next, *nh_tmp;
> > +	LIST_HEAD(tmp);
> > +	int err;
> > +
> > +	list_for_each_entry_safe(nh, nh_next, rt6_nh_list, next) {
> > +		struct fib6_info *rt = nh->fib6_info;
> > +
> > +		err = ip6_route_info_create_nh(rt, &nh->r_cfg, extack);
> > +		if (err) {
> > +			nh->fib6_info = NULL;
> > +			goto err;
> > +		}
> > +
> > +		rt->fib6_nh->fib_nh_weight = nh->weight;
> > +
> > +		list_move_tail(&nh->next, &tmp);
> > +
> > +		list_for_each_entry(nh_tmp, rt6_nh_list, next) {
> > +			/* check if fib6_info already exists */
> > +			if (rt6_duplicate_nexthop(nh_tmp->fib6_info, rt)) {
> > +				err = -EEXIST;
> > +				goto err;
> > +			}
> > +		}
> > +	}
> > +out:
> > +	list_splice(&tmp, rt6_nh_list);
> > +	return err;
> 
> Hi Kuniyuki-san,
> 
> Perhaps it can't happen in practice,

Yes, it never happens by patch 1 as rtm_to_fib6_multipath_config()
returns an error in such a case.


> but if the loop above iterates zero
> times then err will be used uninitialised. As it's expected that err is 0
> here, perhaps it would be simplest to just:
> 
> 	return 0;

If we want to return 0 above, we need to duplicate list_splice() at
err: and return err; there.  Or initialise err = 0, but this looks
worse to me.

Btw, was this caught by Smatch, Coverity, or something ?  I don't
see such a report at CI.
https://patchwork.kernel.org/project/netdevbpf/patch/20250409011243.26195-11-kuniyu@amazon.com/

If so, I'm just curious if we have an official guideline for
false-positives flagged by such tools, like we should care about it
while writing a code and should try to be safer to make it happy.

We are also running Coverity for the mainline kernel and have tons
of false-positive reports due to lack of contexts.

Thanks!

> 
> > +err:
> > +	ip6_route_mpath_info_cleanup(rt6_nh_list);
> > +	goto out;

  reply	other threads:[~2025-04-11 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  1:12 [PATCH v2 net-next 00/14] ipv6: No RTNL for IPv6 routing table Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 01/14] ipv6: Validate RTA_GATEWAY of RTA_MULTIPATH in rtm_to_fib6_config() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 02/14] ipv6: Get rid of RTNL for SIOCDELRT and RTM_DELROUTE Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 03/14] ipv6: Move some validation from ip6_route_info_create() to rtm_to_fib6_config() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 04/14] ipv6: Check GATEWAY in rtm_to_fib6_multipath_config() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 05/14] ipv6: Move nexthop_find_by_id() after fib6_info_alloc() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 06/14] ipv6: Split ip6_route_info_create() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 07/14] ipv6: Preallocate rt->fib6_nh->rt6i_pcpu in ip6_route_info_create() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 08/14] ipv6: Preallocate nhc_pcpu_rth_output " Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 09/14] ipv6: Don't pass net to ip6_route_info_append() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 10/14] ipv6: Factorise ip6_route_multipath_add() Kuniyuki Iwashima
2025-04-11 10:34   ` Simon Horman
2025-04-11 19:33     ` Kuniyuki Iwashima [this message]
2025-04-14 14:52       ` Simon Horman
2025-04-14 18:06         ` Kuniyuki Iwashima
2025-04-15 18:38           ` Simon Horman
2025-04-09  1:12 ` [PATCH v2 net-next 11/14] ipv6: Protect fib6_link_table() with spinlock Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 12/14] ipv6: Defer fib6_purge_rt() in fib6_add_rt2node() to fib6_add() Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 13/14] ipv6: Protect nh->f6i_list with spinlock and flag Kuniyuki Iwashima
2025-04-09  1:12 ` [PATCH v2 net-next 14/14] ipv6: Get rid of RTNL for SIOCADDRT and RTM_NEWROUTE 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=20250411193347.47836-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.