From owner-freebsd-current  Thu Dec 25 00:06:19 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA28711
          for current-outgoing; Thu, 25 Dec 1997 00:06:19 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28695
          for <current@freebsd.org>; Thu, 25 Dec 1997 00:06:15 -0800 (PST)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id XAA29878;
	Wed, 24 Dec 1997 23:50:54 -0800 (PST)
Received: from UNKNOWN(), claiming to be "current1.whistle.com"
 via SMTP by alpo.whistle.com, id smtpd029876; Wed Dec 24 23:50:50 1997
Date: Wed, 24 Dec 1997 23:47:57 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: David Greenman <dg@root.com>
cc: Gary Palmer <gjp@erols.com>, current@freebsd.org
Subject: Re: crash (in networking code?) 
In-Reply-To: <199712250709.XAA16844@implode.root.com>
Message-ID: <Pine.BSF.3.95.971224234536.17456F-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

ignore my previous mail
I just got your commit message.

I think this is a worry. I need to check a bunch of code against 
this possibility. (MALLOC in splnet allowing un-expected re-enterence)

julian