From owner-freebsd-current  Fri May  7  5:58:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 7DDBF14CC9
	for <current@freebsd.org>; Fri,  7 May 1999 05:58:10 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id FAA96664
	for <current@freebsd.org>; Fri, 7 May 1999 05:58:42 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: current@freebsd.org
Subject: somebody has broken sysctlbyname() in -current
Date: Fri, 07 May 1999 05:58:41 -0700
Message-ID: <96660.926081921@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

How to repeat symptoms:

    boot -c
    <make some changes, quit and come up normally>
    kget

Watch your system panic when kget does a:

      sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL);

where len has been properly fetched in a previous syctlbyname()
call (1526 bytes, in my test case) and buf allocated appropriately.
System will panic with a supervisor read, page not present.

In fact, I've just proven the hard way that trying to read
machdep.uc_devlist in any way, including sysctl -a, does the same
thing.  Wurgh. :)

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message