From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 318CCC43381 for ; Mon, 1 Apr 2019 21:54:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 04CA820856 for ; Mon, 1 Apr 2019 21:54:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725893AbfDAVyj (ORCPT ); Mon, 1 Apr 2019 17:54:39 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:38690 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725869AbfDAVyj (ORCPT ); Mon, 1 Apr 2019 17:54:39 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::d71]) (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 D960C108DB210; Mon, 1 Apr 2019 14:54:38 -0700 (PDT) Date: Mon, 01 Apr 2019 14:54:37 -0700 (PDT) Message-Id: <20190401.145437.2134488362479492905.davem@davemloft.net> To: f.fainelli@gmail.com Cc: zenczykowski@gmail.com, maze@google.com, netdev@vger.kernel.org Subject: Re: [PATCH 1/2] net: enable IPv6 iff IPv4 From: David Miller In-Reply-To: References: <20190401194459.168345-1-zenczykowski@gmail.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]); Mon, 01 Apr 2019 14:54:39 -0700 (PDT) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org From: Florian Fainelli Date: Mon, 1 Apr 2019 14:37:25 -0700 > There are tons of systems where IPv6 will likely never be used, let's > face it, so why kill the ability to insmod the IPv6 stack since it > really does not come at the cost of trying to fix the unloading part > already? > > I am not convinced this is solving any problems TBH... I agree. Saying everyone must be doing ipv6 3 to 4 years from now is the height of arrogance. And maybe it is this arrogance of people pushing ipv6 that blocks widespread ipv6 adoption rather than any technical reasons. That's nice on your network, but don't tell me what's appropriate or useful on mine. And ironically the "don't tell me what to do on my network" argument was used as justification for this change. It cuts both ways.