All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: nicolas.dichtel@6wind.com, dsa@cumulusnetworks.com,
	netdev@vger.kernel.org, hannes@redhat.com
Subject: Re: [PATCH net-next v5] net: ipv6: Make address flushing on ifdown optional
Date: Wed, 14 Oct 2015 05:18:14 -0700 (PDT)	[thread overview]
Message-ID: <20151014.051814.801287755321309990.davem@davemloft.net> (raw)
In-Reply-To: <1444820621.2175377.409880265.37A31E2D@webmail.messagingengine.com>

From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 14 Oct 2015 13:03:41 +0200

> On Wed, Oct 14, 2015, at 12:08, Nicolas Dichtel wrote:
>> Le 14/10/2015 11:34, Hannes Frederic Sowa a écrit :
>> [sni]
>> > This sysctl is on my list to be enabled soon by default by any systemd
>> > based distribution. For that reason, could you maybe remove all the
>> I'm not sure to understand why we add a sysctl then. Or at least, why the
>> linux
>> default value is different from all standard distrib. I will be like
>> rp_filter :/
> 
> The difference is that people upgrade (in case of fedora they get a
> .rpmnew file) or install a distribution and don't wonder or have
> assumptions about old behavior. In case companies integrate kernel in
> products/appliances without a way to manage those sysctls we cannot
> simply change them as this would break assumptions for them. I think
> those are two different cases.

The thing that is similar is that people set rp_filter inappropriately
(no end host should have that knob enabled, ever, it's totally
unnecesary).  And the risk here is similar, distribution X will set it
so Y will say "we probably should set it too even though we really
don't understand it fully".

I really hate situations like this.

  reply	other threads:[~2015-10-14 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 16:33 [PATCH net-next v5] net: ipv6: Make address flushing on ifdown optional David Ahern
2015-10-14  1:45 ` David Miller
2015-10-14  9:34   ` Hannes Frederic Sowa
2015-10-14 10:08     ` Nicolas Dichtel
2015-10-14 11:03       ` Hannes Frederic Sowa
2015-10-14 12:18         ` David Miller [this message]
2015-10-14 12:14           ` Hannes Frederic Sowa
2015-10-14 13:00             ` David Miller
2015-10-14 16:09     ` David Ahern
2015-10-15  1:06       ` David Miller
2015-10-15  2:46         ` David Ahern

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=20151014.051814.801287755321309990.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=hannes@redhat.com \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.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.