From owner-cvs-all Fri Oct 12 2:16:42 2001 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 102DA37B408; Fri, 12 Oct 2001 02:16:37 -0700 (PDT) Received: (from roam@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9C9Gbl49976; Fri, 12 Oct 2001 02:16:37 -0700 (PDT) (envelope-from roam) Message-Id: <200110120916.f9C9Gbl49976@freefall.freebsd.org> From: Peter Pentchev Date: Fri, 12 Oct 2001 02:16:37 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/kern kern_sysctl.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG roam 2001/10/12 02:16:37 PDT Modified files: sys/kern kern_sysctl.c Log: Remove the panic when trying to register a sysctl with an oid too high. This stops panics on unloading modules which define their own sysctl sets. However, this also removes the protection against somebody actually defining a static sysctl with an oid in the range of the dynamic ones, which would break badly if there is already a dynamic sysctl with the requested oid. Apparently, the algorithm for removing sysctl sets needs a bit more work. For the present, the panic I introduced only leads to Bad Things (tm). Submitted by: many users of -current :( Pointy hat to: roam (myself) for not testing rev. 1.112 enough. Revision Changes Path 1.117 +7 -3 src/sys/kern/kern_sysctl.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message