From owner-cvs-src@FreeBSD.ORG  Tue Oct 28 09:31:12 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id CE61516A4CF; Tue, 28 Oct 2003 09:31:12 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DB5F643FE1; Tue, 28 Oct 2003 09:31:10 -0800 (PST)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id CF6F62ED43E; Tue, 28 Oct 2003 09:31:10 -0800 (PST)
Date: Tue, 28 Oct 2003 09:31:10 -0800
From: Alfred Perlstein <bright@mu.org>
To: Robert Watson <rwatson@freebsd.org>
Message-ID: <20031028173110.GE6725@elvis.mu.org>
References: <20031026145418.G16944@gamplex.bde.org>
	<Pine.NEB.3.96L.1031026014144.74063M-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.3.96L.1031026014144.74063M-100000@fledge.watson.org>
User-Agent: Mutt/1.4.1i
cc: cvs-src@freebsd.org
cc: src-committers@freebsd.org
cc: cvs-all@freebsd.org
cc: Bruce Evans <bde@zeta.org.au>
Subject: Re: cvs commit: src/sys/kern kern_sig.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2003 17:31:13 -0000

* Robert Watson <rwatson@freebsd.org> [031025 23:46] wrote:
> 
> > How would a mere flag help fix the real complexities for nfs?
> 
> Well, the point of the locking originally introduced in the core dump code
> was presumably to help avoid a common case scenario: corrupted core dumps
> due to parallel dumping.  Given the difficulty in addressing the problem

Actually a DoS like situation where tons of cores are running at the
same time is really the problem.