From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v2 net-next] net/ipv6: Do not allow route add with a device that is down Date: Wed, 24 Jan 2018 09:09:44 -0800 Message-ID: <20180124090944.217c14b7@xeon-e3> References: <20180124162924.6984-1-dsahern@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org, idosch@mellanox.com, roopa@cumulusnetworks.com To: David Ahern Return-path: Received: from mail-pg0-f66.google.com ([74.125.83.66]:36128 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934303AbeAXRJr (ORCPT ); Wed, 24 Jan 2018 12:09:47 -0500 Received: by mail-pg0-f66.google.com with SMTP id k68so3136821pga.3 for ; Wed, 24 Jan 2018 09:09:47 -0800 (PST) In-Reply-To: <20180124162924.6984-1-dsahern@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 24 Jan 2018 08:29:24 -0800 David Ahern wrote: > IPv6 allows routes to be installed when the device is not up (admin up). > Worse, it does not mark it as LINKDOWN. IPv4 does not allow it and really > there is no reason for IPv6 to allow it, so check the flags and deny if > device is admin down. > > Signed-off-by: David Ahern > --- > v2 > - missed setting err to -ENETDOWN (thanks for catching that Roopa) > > net/ipv6/route.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/net/ipv6/route.c b/net/ipv6/route.c > index f85da2f1e729..4e8fab766018 100644 > --- a/net/ipv6/route.c > +++ b/net/ipv6/route.c > @@ -2734,6 +2734,12 @@ static struct rt6_info *ip6_route_info_create(struct fib6_config *cfg, > if (!dev) > goto out; > > + err = -ENETDOWN; > + if (!(dev->flags & IFF_UP)) { > + NL_SET_ERR_MSG(extack, "Nexthop device is not up"); > + goto out; > + } > + > if (!ipv6_addr_any(&cfg->fc_prefsrc)) { > if (!ipv6_chk_addr(net, &cfg->fc_prefsrc, dev, 0)) { > NL_SET_ERR_MSG(extack, "Invalid source address"); This looks like a good idea. There are two equal ways to check for admin up. Either the dev flags or look at link state via netif_running(). Maybe the latter would be better.