From owner-freebsd-current  Tue Jun 23 20:23:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA10800
          for freebsd-current-outgoing; Tue, 23 Jun 1998 20:23:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from puck.nether.net (jared@puck.nether.net [204.42.254.5])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10776
          for <freebsd-current@freebsd.org>; Tue, 23 Jun 1998 20:22:44 -0700 (PDT)
          (envelope-from jared@puck.nether.net)
Received: (from jared@localhost) by puck.nether.net (8.9.0/8.7.3) id XAA21533; Tue, 23 Jun 1998 23:22:41 -0400
Message-ID: <19980623232240.A21485@puck.nether.net>
Date: Tue, 23 Jun 1998 23:22:40 -0400
From: Jared Mauch <jared@puck.nether.net>
To: freebsd-current@FreeBSD.ORG
Subject: Problems w/ IMCP sockets
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	I'm finding that if I set the hold queue too high on an ICMP socket,
and you have *many, many,many* icmp sockets open with these options set,
it can cause the kernel to panic.  Can someone confirm this?  I can see
about doing a specific test program that will exhibit the bug...

	the kernel ends up dying.

	any ideas?

	- jared

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