From owner-freebsd-bugs@FreeBSD.ORG Thu Jan 10 23:01:27 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA63916A420 for ; Thu, 10 Jan 2008 23:01:27 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2F6D913C458; Thu, 10 Jan 2008 23:01:26 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4786A3C6.6080206@FreeBSD.org> Date: Fri, 11 Jan 2008 00:01:26 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Mark Andrews References: <200801102254.m0AMssWo045381@drugs.dv.isc.org> In-Reply-To: <200801102254.m0AMssWo045381@drugs.dv.isc.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/118626: Bad interaction between SIGPIPE and threads. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2008 23:01:27 -0000 Mark Andrews wrote: >> David Schultz wrote: >>> On Thu, Dec 13, 2007, Mark Andrews wrote: >>>> The following reply was made to PR kern/118626; it has been noted by GNATS >> . >>>> From: Mark Andrews >>>> To: bug-followup@FreeBSD.org, marka@isc.org >>>> Cc: sobomax@freebsd.org >>>> Subject: Re: kern/118626: Bad interaction between SIGPIPE and threads. >>>> Date: Thu, 13 Dec 2007 11:41:16 +1100 >>>> >>>> I'll definitely try it. >>>> >>>> The man page for socket(2) should be updated to reference SO_NOSIGPIPE >>>> where it talks about SIGPIPE being generated. >>> The commit log says SO_NOSIGPIPE exists for compatibility, but it >>> looks fully implemented and supported. I've cc'd the original >>> author to find out if there's any good reason not to document it. >> It definitely should be documented fully. Converting threaded >> applications to use this can significantly reduce the lock contention >> associated with signal delivery and associated processing, and may >> improve performance. >> >> Kris > > FYI: libisc and libbind will both being using SO_NOSIGPIPE when it > is available as it is the only way to make the libraries safe in a > threaded envirionment without impacting on the applications use of > SIGPIPE. Yeah, that's another excellent point. Kris