From owner-svn-src-all@FreeBSD.ORG Fri May 22 15:34:22 2009 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2A2D106564A; Fri, 22 May 2009 15:34:22 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7F6E28FC16; Fri, 22 May 2009 15:34:22 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (cm-84.215.252.34.getinternet.no [84.215.252.34]) by smtp.des.no (Postfix) with ESMTP id 9C3BE6D41C; Fri, 22 May 2009 17:34:21 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 94BF28450C; Fri, 22 May 2009 17:34:21 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Baldwin References: <200905201858.n4KIw7Fc040619@svn.freebsd.org> <86r5yhzaso.fsf@ds4.des.no> <200905221118.48669.jhb@freebsd.org> Date: Fri, 22 May 2009 17:34:21 +0200 In-Reply-To: <200905221118.48669.jhb@freebsd.org> (John Baldwin's message of "Fri, 22 May 2009 11:18:48 -0400") Message-ID: <8663ftw3r6.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: svn-src-head@freebsd.org, Rick Macklem , svn-src-all@freebsd.org, Rick Macklem , src-committers@freebsd.org Subject: Re: svn commit: r192463 - head/sys/fs/nfsserver X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 15:34:23 -0000 John Baldwin writes: > What about a malicious denial-of-service attack where a malicious client= =20 > initiates an endless stream of connection attempts to force a panic? I t= hink=20 > that is where the concern lies. I'm sure a malicious client could do it= =20 > intentionally in less than 136 years, perhaps on the order of seconds and= /or=20 > minutes? :) Not quite - 49 days at 1,000 requests per second. I agree that it's very unlikely, but the idea of a cpu_reboot() just rubs me the wrong way. We're painting bikesheds here, though. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no