From owner-freebsd-bugs Sat Sep 15 10:20: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CF4A137B409 for ; Sat, 15 Sep 2001 10:20:01 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8FHK1t27936; Sat, 15 Sep 2001 10:20:01 -0700 (PDT) (envelope-from gnats) Date: Sat, 15 Sep 2001 10:20:01 -0700 (PDT) Message-Id: <200109151720.f8FHK1t27936@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Maxime Henrion Subject: Re: kern/30592: [PATCH] panic: static sysctl oid too high: 684 - when unloading snd_es137x Reply-To: Maxime Henrion Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/30592; it has been noted by GNATS. From: Maxime Henrion To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/30592: [PATCH] panic: static sysctl oid too high: 684 - when unloading snd_es137x Date: Sat, 15 Sep 2001 19:11:14 +0200 Hi, After reading sysctl_ctx_free(9), I now think my patch is bad. It clearly says that the oid_number is not changed to preserve the order of oids in the tree and sysctl_register_oid() will not panic because it will reuse the existing oid. That means that in my case, the oid was really deleted and I don't knwo why. I hope someone more aware than me will be able to fix it and I will continue to dig into this. Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code Key fingerprint = F9B6 1D5A 4963 331C 88FC CA6A AB50 1EF2 8CBE 99D6 Public Key : http://www.epita.fr/~henrio_m/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message