From owner-freebsd-stable  Sat Jun 29 10:40:26 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA16642
          for stable-outgoing; Sat, 29 Jun 1996 10:40:26 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16637
          for <stable@FreeBSD.org>; Sat, 29 Jun 1996 10:40:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id KAA00298; Sat, 29 Jun 1996 10:38:49 -0700 (PDT)
Message-Id: <199606291738.KAA00298@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Juergen Lock <nox@jelal.hb.north.de>
cc: stable@FreeBSD.org, jhay@mikom.csir.co.za
Subject: Re: lockups. 
In-reply-to: Your message of "Sat, 29 Jun 1996 14:06:32 +0200."
             <199606291206.OAA03333@saturn.hb.north.de> 
From: David Greenman <davidg@root.com>
Reply-To: davidg@root.com
Date: Sat, 29 Jun 1996 10:38:49 -0700
Sender: owner-stable@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> the good news is now the system is still up after that so maybe it was
>really only the null check that was missing?
>
> cheers
>	Juergen
>
>PS: now who dares to test this version on something like a real busy
>news server? ;)

   No need to. I saw the same panic and fixed the bug last night in both
-current and -stable. It was, indeed, simply a missing check for NULL. The
problem was introduced a few days ago while fixing a different bug.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project