From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Abramo Bagnara <abramo.bagnara@libero.it>
Cc: ak@suse.de, mbligh@aracnet.com, linux-kernel@vger.kernel.org
Subject: Re: [Bug 420] New: Divide by zero (/proc/sys/net/ipv4/neigh/DEV/base_reachable_time)
Date: Fri, 28 Feb 2003 14:26:25 -0800 [thread overview]
Message-ID: <20030228142625.1a53da75.rddunlap@osdl.org> (raw)
In-Reply-To: <3E5FE165.C8BABD4@libero.it>
On Fri, 28 Feb 2003 23:23:33 +0100
Abramo Bagnara <abramo.bagnara@libero.it> wrote:
| Andi Kleen wrote:
| >
| > "Martin J. Bligh" <mbligh@aracnet.com> writes:
| > >
| > > echo 0 > /proc/sys/net/ipv4/neigh/DEV/base_reachable_time
| > >
| > > But neigh_rand_reach_time() divide by its argument.
| > >
| > > unsigned long neigh_rand_reach_time(unsigned long base)
| > > {
| > > return (net_random() % base) + (base>>1);
| > > }
| >
| > Don't do that then. The sysctl is root-only. There are lots of ways to
| > break the system by writing bogus values into root only configuration
| > options. That is why they are root only
| >
| > I would close the report as WONTFIX.
|
| Don't this argument bring to the weird equality:
|
| root user == infallible guy
|
| IMHO the "if you make a typo you crash the machine" should be avoided
| (at least when feasible without drawbacks).
I agree with that.
It's worth making a patch and letting the maintainer reject it.
Of course, there are still plenty of other ways to write to /proc and kill
the system.
--
~Randy
next prev parent reply other threads:[~2003-02-28 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27440000.1046453828@[10.10.2.4].suse.lists.linux.kernel>
2003-02-28 18:31 ` [Bug 420] New: Divide by zero (/proc/sys/net/ipv4/neigh/DEV/base_reachable_time) Andi Kleen
2003-02-28 22:23 ` Abramo Bagnara
2003-02-28 22:26 ` Randy.Dunlap [this message]
2003-02-28 22:37 ` Robert Love
2003-02-28 17:37 Martin J. Bligh
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=20030228142625.1a53da75.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=abramo.bagnara@libero.it \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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