From owner-freebsd-current@FreeBSD.ORG Wed Oct 4 20:39:06 2006 Return-Path: X-Original-To: current@FreeBSD.org 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 B596216A47B; Wed, 4 Oct 2006 20:39:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 738F743D5C; Wed, 4 Oct 2006 20:39:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5C99F1A4D83; Wed, 4 Oct 2006 13:39:06 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DA54451567; Wed, 4 Oct 2006 16:39:05 -0400 (EDT) Date: Wed, 4 Oct 2006 16:39:05 -0400 From: Kris Kennaway To: Kris Kennaway Message-ID: <20061004203905.GA38810@xor.obsecurity.org> References: <20061004203715.GA38692@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <20061004203715.GA38692@xor.obsecurity.org> User-Agent: Mutt/1.4.2.2i Cc: davidxu@FreeBSD.org, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 20:39:06 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 04, 2006 at 04:37:15PM -0400, Kris Kennaway wrote: > When running stress2 I got an unkillable process stuck in the aioprn > state: >=20 > #0 sched_switch (td=3D0xc5652bd0, newtd=3D0xc4916a20, flags=3D1) at atom= ic.h:265 > #1 0xc0549b96 in mi_switch (flags=3D1, newtd=3D0x0) at ../../../kern/ker= n_synch.c:425 > #2 0xc056baa6 in sleepq_switch (wchan=3D0x0) at ../../../kern/subr_sleep= queue.c:450 > #3 0xc056bc9b in sleepq_timedwait (wchan=3D0xc5668c80) at ../../../kern/= subr_sleepqueue.c:567 > #4 0xc054959e in msleep (ident=3D0xc5668c80, mtx=3D0xc5c6ee0c, priority= =3D76, wmesg=3D0xc0763914 "aioprn", timo=3D100) > at ../../../kern/kern_synch.c:207 > #5 0xc05a0597 in aio_proc_rundown (arg=3D0x0, p=3D0xc5668b04) at ../../.= ./kern/vfs_aio.c:699 > #6 0xc0524769 in exit1 (td=3D0xc5652bd0, rv=3D9) at ../../../kern/kern_e= xit.c:237 > #7 0xc0545eab in sigexit (td=3D0xc5652bd0, sig=3D9) at ../../../kern/ker= n_sig.c:2883 > #8 0xc0546c3b in postsig (sig=3D9) at ../../../kern/kern_sig.c:2765 > #9 0xc056e503 in ast (framep=3D0xed16dd38) at ../../../kern/subr_trap.c:= 270 > #10 0xc06ff61d in doreti_ast () at ../../../i386/i386/exception.s:284 >=20 > This was from the 'random syscall' test, so chances are there is some > insufficient error handling of invalid data here. The syscall in question was aio_read Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFJBvpWry0BWjoQKURAi9EAKCJnTujG1byQPF6JR3Xt9spwdMcugCfdbQU UuD7B7Uas45KdyEVHRrFHN4= =SFDN -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--