From owner-freebsd-current@FreeBSD.ORG  Thu Oct  5 00:19:59 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from localhost.my.domain (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id 5A96416A416;
	Thu,  5 Oct 2006 00:19:58 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
From: David Xu <davidxu@freebsd.org>
To: Kris Kennaway <kris@obsecurity.org>
Date: Thu, 5 Oct 2006 08:19:53 +0800
User-Agent: KMail/1.8.2
References: <20061004203715.GA38692@xor.obsecurity.org>
In-Reply-To: <20061004203715.GA38692@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610050819.53832.davidxu@freebsd.org>
Cc: current@freebsd.org
Subject: Re: Thread stuck in aioprn
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Oct 2006 00:19:59 -0000

On Thursday 05 October 2006 04:37, Kris Kennaway wrote:
> When running stress2 I got an unkillable process stuck in the aioprn
> state:
>
> #0  sched_switch (td=0xc5652bd0, newtd=0xc4916a20, flags=1) at atomic.h:265
> #1  0xc0549b96 in mi_switch (flags=1, newtd=0x0) at
> ../../../kern/kern_synch.c:425 #2  0xc056baa6 in sleepq_switch (wchan=0x0)
> at ../../../kern/subr_sleepqueue.c:450 #3  0xc056bc9b in sleepq_timedwait
> (wchan=0xc5668c80) at ../../../kern/subr_sleepqueue.c:567 #4  0xc054959e in
> msleep (ident=0xc5668c80, mtx=0xc5c6ee0c, priority=76, wmesg=0xc0763914
> "aioprn", timo=100) at ../../../kern/kern_synch.c:207
> #5  0xc05a0597 in aio_proc_rundown (arg=0x0, p=0xc5668b04) at
> ../../../kern/vfs_aio.c:699 #6  0xc0524769 in exit1 (td=0xc5652bd0, rv=9)
> at ../../../kern/kern_exit.c:237 #7  0xc0545eab in sigexit (td=0xc5652bd0,
> sig=9) at ../../../kern/kern_sig.c:2883 #8  0xc0546c3b in postsig (sig=9)
> at ../../../kern/kern_sig.c:2765 #9  0xc056e503 in ast (framep=0xed16dd38)
> at ../../../kern/subr_trap.c:270 #10 0xc06ff61d in doreti_ast () at
> ../../../i386/i386/exception.s:284
>
> This was from the 'random syscall' test, so chances are there is some
> insufficient error handling of invalid data here.
>
> Kris

Are you using aio with non-disk file ? I know it is not safe to use
aio with socket, pipe, fifo, etcs, only disk file may be safe.

David Xu