From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Rick Jones <rick.jones2@hp.com>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: wither bounds checking for networking sysctls
Date: Thu, 30 Aug 2007 20:59:39 -0700 [thread overview]
Message-ID: <20070830205939.2f85a567@localhost> (raw)
In-Reply-To: <46D76A3D.9090207@hp.com>
On Thu, 30 Aug 2007 18:09:17 -0700
Rick Jones <rick.jones2@hp.com> wrote:
> While messing about with "sysctl_tcp_rto_min" I went back and forth a
> bit as to whether there should have been bounds checking (as did some of
> the folks who did some internal review for me). That leads to the
> question - is it considered worthwhile to add a bit more bounds checking
> to sundry networking sysctls?
>
> rick jones
IMHO As long as the any value from sysctl doesn't crash kernel, we
should let it go. Enforcing RFC policy or inter-dependencies seems
likes a useless exercise.
next prev parent reply other threads:[~2007-08-31 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 1:09 wither bounds checking for networking sysctls Rick Jones
2007-08-31 3:59 ` Stephen Hemminger [this message]
2007-08-31 17:14 ` Rick Jones
2007-09-09 15:26 ` Eric W. Biederman
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=20070830205939.2f85a567@localhost \
--to=shemminger@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 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).