From owner-freebsd-bugs  Tue Jun  2 13:10:41 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA01350
          for freebsd-bugs-outgoing; Tue, 2 Jun 1998 13:10:41 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01325
          for <freebsd-bugs@FreeBSD.org>; Tue, 2 Jun 1998 13:10:35 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id NAA16779;
	Tue, 2 Jun 1998 13:10:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA29597;
          Tue, 2 Jun 1998 13:02:47 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199806022002.NAA29597@hub.freebsd.org>
Date: Tue, 2 Jun 1998 13:02:47 -0700 (PDT)
From: cmetz@inner.net
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/6837: in_setpeeraddr() and in_setsockaddr() block on memory
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         6837
>Category:       kern
>Synopsis:       in_setpeeraddr() and in_setsockaddr() block on memory
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun  2 13:10:00 PDT 1998
>Last-Modified:
>Originator:     Craig Metz
>Organization:
NRL
>Release:        3.0-SNAP
>Environment:
>Description:
These two functions now MALLOC their address parameter inline rather
than having the address buffer passed in. They do so with M_WAITOK,
which will tsleep() the process indefinitely waiting for the memory.
Granted, if you're that short on memory on a BSD system, you'll have
bigger problems, but IMO these functions should kick ENOBUFS back up the
stack and get out of kernel mode (thus freeing up some other buffer
memory) rather than block the process.

>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:

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