From owner-freebsd-hackers Thu Jan 27 0:19:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B90414A27 for ; Thu, 27 Jan 2000 00:19:25 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 295482DC0B; Thu, 27 Jan 2000 09:18:58 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id D14937811; Thu, 27 Jan 2000 09:18:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id CF03510E10; Thu, 27 Jan 2000 09:18:16 +0100 (CET) Date: Thu, 27 Jan 2000 09:18:16 +0100 (CET) From: Andrzej Bialecki To: Matthew Dillon Cc: Scott Hess , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read crashing certain kernels. In-Reply-To: <200001270457.UAA18887@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Matthew Dillon wrote: > This is an incredibly scary program! It's sending an iocb to aio_read > and then pops the stack and exits. The act of exiting could very well > scribble all over the iocb structure while the I/O is in progress and, > of course, then the program invalidates the stack and exits. Even if that's the case, it's still a userland program that is able to panic the system. So, no matter what the program does, it's still a bug in the way we handle aio. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message