From owner-freebsd-smp Thu Sep 7 20:29:33 2000 Delivered-To: freebsd-smp@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id DEE8437B424; Thu, 7 Sep 2000 20:29:28 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e883SrK05070; Fri, 8 Sep 2000 00:28:53 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 00:28:53 -0300 (ADT) From: The Hermit Hacker To: Warner Losh Cc: Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009080314.VAA50701@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Sep 2000, Warner Losh wrote: > In message The Hermit Hacker writes: > : Okay, I'm a little confused here ... from what I'm reading/following, this > : isn't a new problem ... or is it? If not, why has it suddenly manifested > : itself with the new SMP code? > > It seems to be new with the SMP code. At least that's what my reading > of the original message is. That was what I thought when I wrote the original message ... it just scares me sometimes how quickly things get acknowledged as a problem in the Open Source community, especially after dealign with tech support at Sun and getting the complete run around ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message