Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp1641imb; Thu, 28 Feb 2019 14:05:58 -0800 (PST) X-Google-Smtp-Source: APXvYqzzrEiuCeZH2ng0TqtQetl2iWJD2iFho/mswiMEtkHT0bgogP3Ph/agof9QTo4Pe8d45pHk X-Received: by 2002:a63:81c7:: with SMTP id t190mr1444821pgd.166.1551391558416; Thu, 28 Feb 2019 14:05:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551391558; cv=none; d=google.com; s=arc-20160816; b=LENwZm/y4ObwnpeN9Kl69tWdxx6PIfmCH5at0zUFUtDhPgAU0ph8JsQsFSA5UsHwD5 nossS/mTlGwXZQdJDDpjfTRYmPQvJD7jSXyD+uzik2m0awdqGOA2gsdhx8BvxQit6ZVx Hqbxo/rydEYfIgTEnbUIvksWw1zDnO6lV/ZHtHkmr8RGaPjqE6W+xZivPJk4VNhjSsOZ eBmjSexd/FK3ZB5/GEK5lgCCEURr9wkJR3pMX2R5n6V7CiCKAUhla+L/lTPgyhcLSXVC X6R0TM01/9ajwK/nUQSDZV9AwqDcfHNU7RRNxhriepzPfRTkObZVEj6A16jZ7FylU84t DA7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=xRcDT6yv5GkHyohE2T5/c3SGK/TxyqH4Myly7rp1kq8=; b=B0rjIMdyl2DoxE/whKLXunSHqo//sIYh5NgCXMYED9nfrqgNnQQR7B2UMsp9X3Eq5G 9JZayYLxawZJhSbpq2bNoNYE7+2c9nlGpDAWixWheMwhjdLy4G8nxoyC2aWMbargDrWP LyyASmwhWp0yjj0nlbeP0CIc/zy5JdeeFC52HjI9xrNPOaa+CsYdCmNZHBwHxyZDHFSd 2XPnVAyz9/BQAPPPaXrfjjWaFcMRkkAeVPIS85qxej5ECoB8EHy4lfDIvmcno1Jgn++w D1lQ08Od+SWl2+equtEh7DfMDAkETPMkWqYmruP9hA00ADtnDM85qHDtgxs3p0G6zg05 jQSQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j9si18017892plk.359.2019.02.28.14.05.30; Thu, 28 Feb 2019 14:05:58 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388307AbfB1VCO (ORCPT + 99 others); Thu, 28 Feb 2019 16:02:14 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:38740 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726414AbfB1VCO (ORCPT ); Thu, 28 Feb 2019 16:02:14 -0500 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::bf5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id C788C14BFD00D; Thu, 28 Feb 2019 13:02:13 -0800 (PST) Date: Thu, 28 Feb 2019 13:02:13 -0800 (PST) Message-Id: <20190228.130213.1481374802407995712.davem@davemloft.net> To: fruggeri@arista.com Cc: yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru, maxim@arista.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH] net: ipv6: check net in ip6_call_ra_chain From: David Miller In-Reply-To: <20190228190146.802CD95C016B@us180.sjc.aristanetworks.com> References: <20190228190146.802CD95C016B@us180.sjc.aristanetworks.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 28 Feb 2019 13:02:14 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: fruggeri@arista.com (Francesco Ruggeri) Date: Thu, 28 Feb 2019 11:01:46 -0800 > ip6_call_ra_chain is called when IPv6 packet with Router Alert option > is forwarded. > It needs to check if the net of the socket is the same as the net of the > input device, otherwise the packet gets delivered to every IPv6 socket > listening for Router Alerts, no matter which network namespace it is in. > > Suggested-by: Maxim Martynov > Signed-off-by: Maxim Martynov > Signed-off-by: Francesco Ruggeri Right now someone using such a tool does get all RAs in the system. Your change not only breaks them, but also gives them no method by which to keep obtaining the same behavior. I don't know what to do or suggest in this situation, but right now I'm putting this patch on hold.