Date: Sat, 11 Aug 2007 16:10:06 -0400 (EDT) From: Kirk Russell <kirk@ba23.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: panic: lock "aiomtx" already initialized Message-ID: <Pine.NEB.4.44.0708111606360.26081-100000@greyhawk> In-Reply-To: <20070809034842.GN2738@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Aug 2007, Kostik Belousov wrote: > > This patch should fix the problem: > > diff --git a/sys/kern/vfs_aio.c b/sys/kern/vfs_aio.c > index 7610da8..47580b6 100644 > --- a/sys/kern/vfs_aio.c > +++ b/sys/kern/vfs_aio.c > @@ -719,6 +719,7 @@ restart: > } > AIO_UNLOCK(ki); > taskqueue_drain(taskqueue_aiod_bio, &ki->kaio_task); > + mtx_destroy(&ki->kaio_mtx); > uma_zfree(kaio_zone, ki); > p->p_aioinfo = NULL; > } > > It seems that you shall use a lot of quickly exit()ing processes all of > them using aio to reliable reproduce the problem. I merged your patch into 7.0-CURRENT-200706. I can no longer reproduce the kern/114216 panic using the dt AIO client script. -- Kirk Russell <kirk@ba23.org> http://www.ba23.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.4.44.0708111606360.26081-100000>