From owner-freebsd-bugs  Wed Jun 25 02:00:09 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA11856
          for bugs-outgoing; Wed, 25 Jun 1997 02:00:09 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA11823;
          Wed, 25 Jun 1997 02:00:05 -0700 (PDT)
Date: Wed, 25 Jun 1997 02:00:05 -0700 (PDT)
Message-Id: <199706250900.CAA11823@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: sthaug@nethelp.no
Subject: Re: kern/3925: SO_SNDLOWAT of 0 causes kernel to use 99% of CPU time on TCP send
Reply-To: sthaug@nethelp.no
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3925; it has been noted by GNATS.

From: sthaug@nethelp.no
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: kern/3925: SO_SNDLOWAT of 0 causes kernel to use 99% of CPU time on TCP send
Date: Wed, 25 Jun 1997 10:58:20 +0200

 The problem is now fixed in NetBSD, here is the log message.
 
 Steinar Haug, Nethelp consulting, sthaug@nethelp.no
 ----------------------------------------------------------------------
 thorpej
 Tue Jun 24 13:04:46 PDT 1997
 Update of /cvsroot/src/sys/kern
 In directory netbsd1:/var/slash-tmp/cvs-serv25765
 
 Modified Files:
         uipc_socket.c
 Log Message:
 In sosetopt():
 - Disallow < 1 values for SO_SNDBUF, SO_RCVBUF, SO_SNDLOWAT, and
   SO_RCVLOWAT; return EINVAL if the user attempts to set <= 0.
   Inspired by PR #3770, from Havard Eidnes <he@vader.runit.sintef.no>.
 - For SO_SNDLOWAT and SO_RCVLOWAT, don't let the low-water mark get
   set above the high-water mark.  Behavior is now consistent with
   BSD/OS: If such an attempt is made, silently truncate to the high-water
   value.