From owner-freebsd-bugs@FreeBSD.ORG  Fri Jun 20 20:48:33 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 80A7E37B401; Fri, 20 Jun 2003 20:48:33 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E75E743F85; Fri, 20 Jun 2003 20:48:31 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id NAA16808;
	Sat, 21 Jun 2003 13:48:23 +1000
Date: Sat, 21 Jun 2003 13:48:22 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: "Christian S.J. Peron" <maneo@bsdpro.com>
In-Reply-To: <200306201508.h5KF8Vgc000839@h24-79-64-13.wp.shawcable.net>
Message-ID: <20030621133541.X51140@gamplex.bde.org>
References: <200306201508.h5KF8Vgc000839@h24-79-64-13.wp.shawcable.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-bugs@freebsd.org
cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/53557: [patch]: kernel panic: fix for a divide by zero
 processor exception
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jun 2003 03:48:33 -0000

On Fri, 20 Jun 2003, Christian S.J. Peron wrote:

> >Description:
> 	If root sets the kern.log_wakeups_per_second variable to 0
> 	the next time the callback for the syslog wakeup gets scheduled
> 	it will panic due to divide by zero machine exception.

Don't do that then.

There are hundreds or thousands of sysctls that may be used for much
more interesting foot shooting than a panic.  If foot shooting prevention
is required, then it should be implemented more generally starting
with simple range checks for all sysctls that set scalar values.

Bruce