From: Ani Sinha <ani@arista.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: route/max_size sysctl in ipv4
Date: Thu, 8 Jan 2015 10:39:37 -0800 [thread overview]
Message-ID: <CAOxq_8OPj4twFg2U93hFNSjeiZ5We5DgeCo-W5hSbXJvQmZfyQ@mail.gmail.com> (raw)
In-Reply-To: <1420695665.5947.44.camel@edumazet-glaptop2.roam.corp.google.com>
On Wed, Jan 7, 2015 at 9:41 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2015-01-07 at 19:40 -0800, Ani Sinha wrote:
>
>> true but at least those scripts which does only read the values will
>> continue to function in a child namespace. In our case, our script
>> only reads the max_size sysctl but since it operates from within a
>> child namespace, it doesn't find it.
>>
>> thoughts?
>
> Fix your script,
But the whole point of keeping this sysctl still around is not to
break the userland scripts! If we are trying to achieve that, I think
we should go one step further and make sure that the sysctl is still
available for reading even in child namespaces (as it used to be the
case).
next prev parent reply other threads:[~2015-01-08 18:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 23:48 route/max_size sysctl in ipv4 Ani Sinha
2015-01-06 0:36 ` David Miller
2015-01-06 0:43 ` Ani Sinha
2015-01-06 0:51 ` David Miller
2015-01-06 0:56 ` Ani Sinha
2015-01-06 12:41 ` Pádraig Brady
2015-01-06 17:11 ` Ani Sinha
2015-01-06 18:09 ` Eric Dumazet
2015-01-06 20:05 ` Ani Sinha
2015-01-07 1:56 ` Ani Sinha
2015-01-08 1:25 ` Ani Sinha
2015-01-08 2:19 ` Eric Dumazet
2015-01-08 3:40 ` Ani Sinha
2015-01-08 5:41 ` Eric Dumazet
2015-01-08 18:39 ` Ani Sinha [this message]
2015-01-08 19:03 ` Eric Dumazet
2015-01-08 20:13 ` Ani Sinha
2015-01-08 20:18 ` Eric Dumazet
2015-01-09 18:47 ` Cong Wang
2015-01-09 19:08 ` Ani Sinha
2015-01-09 19:37 ` Cong Wang
2015-01-09 21:23 ` Ani Sinha
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=CAOxq_8OPj4twFg2U93hFNSjeiZ5We5DgeCo-W5hSbXJvQmZfyQ@mail.gmail.com \
--to=ani@arista.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).