From owner-freebsd-current Thu Sep 12 10: 8:23 2002 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 62A7A37B400; Thu, 12 Sep 2002 10:08:21 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D38A43E4A; Thu, 12 Sep 2002 10:08:18 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.11.6/8.11.6) with ESMTP id g8CH89k80595; Thu, 12 Sep 2002 20:08:09 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.12.5/8.12.5) with ESMTP id g8CH8G1X013731; Thu, 12 Sep 2002 20:08:16 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3D80CA46.1AF0CA4A@FreeBSD.org> Date: Thu, 12 Sep 2002 20:09:26 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Maxime Henrion Cc: current@FreeBSD.org Subject: Re: Panic during reboot in vflush() References: <3D8045D3.35A3DECE@FreeBSD.org> <20020912080531.GQ86074@elvis.mu.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxime Henrion wrote: > > Maxim Sobolev wrote: > > Any ideas? > > Looks like some other processes was modifying the mountlist while > vfs_unmountall() was running. Is this an SMP box ? No, it's UP. > It would be nice if > you could check in gdb which other process was holding the mountlist_mtx > mutex if any. Sure, if you will provide me with instruction on how to do in. > The vfs_unmountall() function doesn't acquire the > mounstlist_mtx and states this is OK in a comment because this functions > is ran upon reboot, but I suspect this is incorrect and we still need to > do the locking. I'll write a patch tonight to add locking into > vfs_unmountall(), but it may be hard to test unless you know of a way to > reproduce this panic easily. No, I don't. It's the first time I've encountered this particular problem. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message