From patchwork Mon Apr 24 15:09:09 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: David Ahern X-Patchwork-Id: 754297 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3wBV9s4Q3dz9sN8 for ; Tue, 25 Apr 2017 01:09:21 +1000 (AEST) Authentication-Results: ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=cumulusnetworks.com header.i=@cumulusnetworks.com header.b="euLebgIl"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1428285AbdDXPJT (ORCPT ); Mon, 24 Apr 2017 11:09:19 -0400 Received: from mail-pf0-f173.google.com ([209.85.192.173]:33354 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1171750AbdDXPJQ (ORCPT ); Mon, 24 Apr 2017 11:09:16 -0400 Received: by mail-pf0-f173.google.com with SMTP id a188so13721606pfa.0 for ; Mon, 24 Apr 2017 08:09:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=from:to:cc:subject:date:message-id; bh=so7mbHGla7ZbQxFOYAKfPFkOWFUseh/RMn1nKvraI3Q=; b=euLebgIlCxVUYDZ3QlSLCFFwii5rIyPKHMj12/CokR9cGkpoBajV51/iXhlAObqNht tZZMZ5WTx+jUtGZhbRVv1RST8kECdBtLEM/tfWMysAldXeq60XgeugRPiM42m3mvDvls UhC0jfMx/dTdJD6khbjn9HYyoHzsAFzPOrQGs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=so7mbHGla7ZbQxFOYAKfPFkOWFUseh/RMn1nKvraI3Q=; b=W60vK7W9konR5ni7MQBoYNKjzRAamB4XIiZWVOxkW86Opc0UWx6F3Fi54m5Kl9Pth1 67L5BdwhwBKw/O/EksSGNuEb6dibYK6bAfyntSxDeKDkcTslN8J7gHJXE4WOl/warIRD BhKrH+8OvjQvel7NJNmwe2ntjd7d+ZCnTYxBhs1XaAdkAO00UqYRQIlKaU7m1brNPGAG LetFcsIkooPGUbt9rUgJXQGcJXyv/Jm9UFI5USbIkmvjY9oJR6FNAGQyg3lsght6RuJk EVmNfdR/6cC+RySWEtzuhFy3/I4jCS55lbf3rADCsj8e3tEmNCMKSXfPnXbD9a9aDz83 mJbA== X-Gm-Message-State: AN3rC/6a0PBExpxvBwdWhqTmh5ljtJB+xRFlBQVF48iodY6Y+Lmn0HXX ElyIH6MZHQ6Gs0RT X-Received: by 10.99.181.18 with SMTP id y18mr24980098pge.192.1493046555696; Mon, 24 Apr 2017 08:09:15 -0700 (PDT) Received: from kenny.it.cumulusnetworks.com. ([216.129.126.126]) by smtp.googlemail.com with ESMTPSA id g71sm30464369pfc.41.2017.04.24.08.09.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Apr 2017 08:09:15 -0700 (PDT) From: David Ahern To: netdev@vger.kernel.org Cc: dvyukov@google.com, andreyknvl@google.com, mmanning@brocade.com, kafai@fb.com, David Ahern Subject: [PATCH v3 net] net: ipv6: regenerate host route if moved to gc list Date: Mon, 24 Apr 2017 08:09:09 -0700 Message-Id: <1493046549-17420-1-git-send-email-dsa@cumulusnetworks.com> X-Mailer: git-send-email 2.1.4 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Taking down the loopback device wreaks havoc on IPv6 routing. By extension, taking down a VRF device wreaks havoc on its table. Dmitry and Andrey both reported heap out-of-bounds reports in the IPv6 FIB code while running syzkaller fuzzer. The root cause is a dead dst that is on the garbage list gets reinserted into the IPv6 FIB. While on the gc (or perhaps when it gets added to the gc list) the dst->next is set to an IPv4 dst. A subsequent walk of the ipv6 tables causes the out-of-bounds access. Andrey's reproducer was the key to getting to the bottom of this. With IPv6, host routes for an address have the dst->dev set to the loopback device. When the 'lo' device is taken down, rt6_ifdown initiates a walk of the fib evicting routes with the 'lo' device which means all host routes are removed. That process moves the dst which is attached to an inet6_ifaddr to the gc list and marks it as dead. The recent change to keep global IPv6 addresses added a new function, fixup_permanent_addr, that is called on admin up. That function restarts dad for an inet6_ifaddr and when it completes the host route attached to it is inserted into the fib. Since the route was marked dead and moved to the gc list, re-inserting the route causes the reported out-of-bounds accesses. If the device with the address is taken down or the address is removed, the WARN_ON in fib6_del is triggered. All of those faults are fixed by regenerating the host route if the existing one has been moved to the gc list, something that can be determined by checking if the rt6i_ref counter is 0. Fixes: f1705ec197e7 ("net: ipv6: Make address flushing on ifdown optional") Reported-by: Dmitry Vyukov Reported-by: Andrey Konovalov Signed-off-by: David Ahern --- v3 - removed 'if (prev)' and just call ip6_rt_put; added comment about spinlock v2 - change ifp->rt under spinlock vs cmpxchg - add comment about rt6i_ref == 0 net/ipv6/addrconf.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c index 80ce478c4851..93f81d9cd85f 100644 --- a/net/ipv6/addrconf.c +++ b/net/ipv6/addrconf.c @@ -3271,14 +3271,25 @@ static void addrconf_gre_config(struct net_device *dev) static int fixup_permanent_addr(struct inet6_dev *idev, struct inet6_ifaddr *ifp) { - if (!ifp->rt) { - struct rt6_info *rt; + /* rt6i_ref == 0 means the host route was removed from the + * FIB, for example, if 'lo' device is taken down. In that + * case regenerate the host route. + */ + if (!ifp->rt || !atomic_read(&ifp->rt->rt6i_ref)) { + struct rt6_info *rt, *prev; rt = addrconf_dst_alloc(idev, &ifp->addr, false); if (unlikely(IS_ERR(rt))) return PTR_ERR(rt); + prev = ifp->rt; + + /* ifp->rt can be accessed outside of rtnl */ + spin_lock(&ifp->lock); ifp->rt = rt; + spin_unlock(&ifp->lock); + + ip6_rt_put(prev); } if (!(ifp->flags & IFA_F_NOPREFIXROUTE)) {