From owner-freebsd-current Thu Dec 19 23:35: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78EE237B401 for ; Thu, 19 Dec 2002 23:35:03 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 913E243EE5 for ; Thu, 19 Dec 2002 23:34:59 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 61256 invoked by uid 1000); 20 Dec 2002 07:35:01 -0000 Date: Thu, 19 Dec 2002 23:35:01 -0800 (PST) From: Nate Lawson To: Sean Kelly Cc: current@freebsd.org Subject: Re: `cat /dev/io` leads to system lockup. In-Reply-To: <20021220062935.GA699@edgemaster.zombie.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Dec 2002, Sean Kelly wrote: > On my 5.0-CURRENT kernel built 45 minutes ago, I can bring my system to its > knees by doing > > # cat /dev/io > > While I understand that this isn't exactly something one would normally be > doing, is it really something that should bring the system down? You're running as root. So does "yes > /dev/da0" and "cat /dev/urandom > /dev/mem" and ... (infinity) -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message