From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 25 15:47:54 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC37A37B401 for ; Fri, 25 Apr 2003 15:47:54 -0700 (PDT) Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E3B443FDF for ; Fri, 25 Apr 2003 15:47:54 -0700 (PDT) (envelope-from drew@revolt.poohsticks.org) Received: from revolt.poohsticks.org (localhost [127.0.0.1]) by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id h3PMlpd17574 for ; Fri, 25 Apr 2003 16:47:51 -0600 (MDT) (envelope-from drew@revolt.poohsticks.org) Message-Id: <200304252247.h3PMlpd17574@revolt.poohsticks.org> From: drew@PoohSticks.ORG To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17571.1051310870.1@revolt.poohsticks.org> Date: Fri, 25 Apr 2003 16:47:50 -0600 Sender: drew@PoohSticks.ORG Subject: Problems with AIO? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2003 22:47:55 -0000 I have a program which needs to do multiple non-blocking disk I/Os in parallel on raw devices, have been using pthreads with wrappers that provide a single-threaded event driven interface, and am in the process of switching to AIO to get rid of some debugger/pthread interactions and make some Windows guys happy because AIO looks more like their async IO interface. So, I look in the LINT config file and see this: # Use real implementations of the aio_* system calls. There are numerous # stability issues in the current aio code that make it unsuitable for # inclusion on shell boxes. options VFS_AIO When I query GNATs for AIO in the single-line text fields, I get just this 2002/01/17] kern/34017 The siginfo_t passed to the signal handling routine is not filled out for AIO and a web search only turns up this exploit http://www.securiteam.com/exploits/6L00E0A3FC.html Are there other bugs I should be aware of? In this case, I'm only using aio_read() and aio_write() on raw disk devices. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible.